Matilda
MATILDA: Multi-AnnoTator multi-language Interactive Lightweight Dialogue Annotator
Install / Use
/learn @Wluper/MatildaREADME

MATILDA: Multi-AnnoTator multi-language Interactive Lightweight Dialogue Annotator
Authors: Davide Cucurnia, Nikolai Rozanov, Irene Sucameli, Augusto Ciuffoletti, Maria Simi
Contact: contact@wluper.com
Paper: link to the EACL paper
Citation at bottom of README! (Please cite when using)
MATILDA is the first multi-annotator, multi-language annotation tool that is built on the top of an open source dialogue annotation tool LIDA, specifically it has full support for multiple annotators, project management and multiple annotation models. It uses MongoDB for data delivery and consistency, it comes with production ready server by using Gunicorn and nginx.
Document structure
- <strong>Requirements</strong>
- <strong>Installation</strong>
- Option A: Running the Server with Docker
- Docker and docker-compose
- Option B: Running the Server with flask (WSGI) or gunicorn
- Downloading & Installing Modules Requirements
- Run the server
- Optional: Installing a MongoDB local database
- Accessing the interface
- First username and password
- Option A: Running the Server with Docker
- <strong>Configuration</strong>
- Network and database
- Annotation Models
- <strong>Advanced Configuration</strong>
- New Labels
- Interannotator Tool
- Adding ML Models As Recommenders
- Dummy Models
- <strong>JSON Format Example</strong>
0. Requirements
In order to run MATILDA on Docker you will need a 64bit system because that's the minimum requirements for Docker. If you wish to use MATILDA with a 32bit system you can just follow the Option B steps. In both cases server needs a minimum of 60MB on the hard disk, plus the space needed for the database.
MATILDA is very light-weight. Containerized with Docker MATILDA smoothly run on a system based on Intel Celeron J3355, a 2-core microprocessor dated 2016 created for entry level PCs, equipped with a 2GB RAM. During a significant processing peak induced with an upload, the footprint did not exceed a few (2-3%) percent of hardware capacity.
1. Installation
MATILDA is a client-server app. The server is written in Python with the Flask web framework. The front end is written with HTML/CSS/Vue.js and communicates with the back end via a RESTful API.
To run MATILDA, you will need to first run the Flask server on your local machine / wherever you want the back end to run.
To do this you have two options:
- Using the provided docker-compose.yml file to run it in a docker container together with its database. This is probably faster and cleaner.
- Otherwise you will need to have Python 3.6 or above installed on your machine and a mongoDB database, either online (there are many free services) or local. If you are using an online database you will need to set the database address in configuration/conf.json.
Further instructions are provided in the next paragraph.
Option A: Running the Server with Docker
MATILDA also comes with a docker container you may want to use for a fast and clean installation on Linux, OSX and Windows systems.
Docker and docker-compose
Simply install docker and docker-compose on your system and run the docker-compose.yml file in the repository as shown above. Using the git command, clone this repository (or download and uncompress the zipfile), and enter the matilda directory.
$ git clone https://github.com/davivcu/matilda
$ cd matilda
$ sudo docker-compose up -d
And it's done!
Stopping the service
Unless you manually stop the service for some reason, it will be automatically started at the next boot. So the server cab be switched off/on without intervention of the administrator.
To manually stop the service use the command:
$ sudo docker-compose kill
<strong> For further details, please see the specific instructions in /docker_readme.md. </strong>
Option B: Running the Server with Flask (WSGI) or Gunicorn
1. Downloading & Installing Modules Requirements
It is strongly recommended that you clone into a Python virtual environment:
$ mkdir MATILDA/
$ python3 -m venv MATILDA/
$ cd MATILDA/ && source bin/activate
(MATILDA)$ git clone https://github.com/davivcu/matilda
(MATILDA)$ cd matilda/web
(MATILDA)$ pip3 install -r requirements.txt
2. Run the server with Flask or Gunicorn
Assuming you have just followed the steps to "Downloading & Installing MATILDA Module Requirements" and you have a mongoDB locally installed on your system:
(MATILDA)$ pwd
~/MATILDA/matilda/web
(MATILDA)$ cd server/
(MATILDA)$ python matilda_app.py
You should see the Flask server running in the Terminal now on port 5000.
Alternatively you may use gunicorn to run the server app:
(MATILDA)$ pwd
~/MATILDA/matilda/web
(MATILDA)$ cd server/
gunicorn --bind localhost:5000 matilda_app:MatildaApp
Optional: Installing a MongoDB local database
<strong>If you don't plan to use a local database but you prefer an online one, feel free to skip this step.</strong>
mongoDB requires Homebrew to install on OSX. Update instructions are on its official website: https://brew.sh/#install
Instructions for a working local mongoDB database are here: https://docs.mongodb.com/manual/administration/install-community/
<strong>Testing:</strong>
You can test it's running by:
ps aux | grep -v grep | grep mongod
Accessing the interface
Each option you chose before you can now simply navigate to http://localhost:5000 if you installed the server locally or navigate to the remote server address. Keep in mind you may need to open the correct ports on your firewall(s) in order to reach the server.
HTTP Requests from your client may not reach your server in some configuration environment,
in those few cases please check and edit the backend address in MATILDA's file /web/server/gui/source/utils/backend.js.
Other configuration options are exposed in /Configuration/conf.json.
First username and password
On its first start MATILDA creates an administrator account with username "admin" and password "admin". You need to use this credentials for your first login. Once you are allowed to enter it's recommended to change the admin password from the graphical interface.
2. Configuration
Network and Database
All configuration changes that you may wish to make to MATILDA network and database can be done by editing the json file
/Configuration/conf.json.
There you can change:
- App ports (default 5000) and address (127.0.0.1)
- Database location with address:port combination (127.0.0.1:27017) or mongoDB URI (mongodb://mongo:27017/?retryWrites=true&w=majority)
- The annotation models you want to be available inside MATILDA. The json files you are referring to must be included in the Configuration folder.
If you are using the Docker version you can also perform additional configuration with /Configuration/gunicorn_run.sh.
Annotation Models
All configuration changes that you may wish to make to MATILDA's annotation model can be done by editing the json file
/Configuration/lida_model.json or by adding a new one. This script contains a configuration dictionary that describes
which labels will appear in MATILDA's front end.
You can also add an entire new annotation model file and put a reference to it in the /Configuration/conf.json file in
order to instruct the program to load it on start.
You can currently add three different types of new labels to MATILDA:
-
multilabel_classification:: will display as checkboxes which you can select one or more of. -
multilabel_classification_string:: will display as checkboxes with values next to them and text input fields for a string. This kind of label would be used for a slot-value pair in dialogue state tracking, where you have the slot name (a classification) and the value (an arbitrary string). -
string:: will display underneath the user's utterance as a string response. This is the label field that would be used for a response to the user's query.
3. Advanced Configuration
New Labels
To add a new label, simply specify a new entry in the configDict in
/web/server/annotator_config.py. The key should be the name of the label, and the
value a dictionary which has a field specifying the label_type, a boolean
field required which defines whether the label is required or not and a field
called labels which specify what label values there are for this label (not
applicable to labels of type string).
You can optionally add a description field and a model field which provides
a recommender for the label (see below for details on API requirement). You can
see examples of all label types in /web/server/annotator_config.py.
The Annotator Config file

Interannotator tool
All configuration changes that you would like to add to the Interannotator tool can be done in /web/server/annotator_config.py.
It currently allows you to modify the following:
- How to treat disagreements etc.
- How to calculate scores.
Adding ML Models As Recommenders
All configuration changes that you may wish to make to MATILDA can be done in the
file /web/server/annotator_config.py. This script contains a configuration
dictionary that describes which labels will appear in MATILDA's front end.
To add a recommender, simply add a field called "model" to the element of the
config dict that you want to add a recommender for. The value of this field
needs to be a Python object that conforms to the interface defined below.
Any recommender you add to MATILDA must conform to the following API: each
recommender is a Python object that has a method called transform:
transform(sent: str) -> List[str] or List[Tuple[str, str]] or str
That is, your recommender only
Related Skills
node-connect
347.2kDiagnose OpenClaw node connection and pairing failures for Android, iOS, and macOS companion apps
claude-opus-4-5-migration
108.0kMigrate prompts and code from Claude Sonnet 4.0, Sonnet 4.5, or Opus 4.1 to Opus 4.5
frontend-design
108.0kCreate distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
model-usage
347.2kUse CodexBar CLI local cost usage to summarize per-model usage for Codex or Claude, including the current (most recent) model or a full model breakdown. Trigger when asked for model-level usage/cost data from codexbar, or when you need a scriptable per-model summary from codexbar cost JSON.
