|Trial Data Ready||
|Training Data Ready||
|Evaluation End||Feb 1 (Wed), 2023|
|System Description Paper Submission Due||Feb 28 (Tue), 2023|
|Notification to Authors||Mar 31 (Fri), 2023|
|Camera-ready Due||Apr 21 (Fri), 2023|
|Workshop||13-14 July 2023 co-located with ACL|
1. How to Participate
- The organizers have defined a task (i.e., NER) and released the training data on September 1st, 2022. The task is divided across several languages as subtasks. The participants can work on as many as languages they want to.
- Participants can form a team with multiple people or single person team is okay.
- The participants can access the training data after filling the form in the Dataset page.
- The participants can experiment with the training data to develop models. Usage of any external data or resource is allowed and highly encouraged. This process can run till the evaluation period.
- Evaluation period: On January 24th, the organizers released the test set containing instances without the labels. The participants will use their developed models to predict the labels for the instances and they have to create a submission file that follows exactly the same format of the training data. These prediction files should be submitted to Codalab submission portal. These predictions will be compared against the ground truth labels of the test data and the teams will be ranked on a leaderboard according to the performance score.
- Each team is encouraged to write a system description paper describing their submission system, analysis of their results, interesting insights and submit before around February 23rd, 2023. Paper submission procedure will be announced later. After a review period, each team has to update their submitted paper based on the review feedback and submit the camera ready version. Accepted papers will be published as part of the proceedings of SemEval 2023 Workshop.
- To connect with the organizers or other participants about any questions or discussions, participants can join the Slack and Google group.
2. Training Data Format
Click here to download a small set of trial data in English.
We will follow the CoNLL format for the datasets. Here is an example data sample from the trial data.
In a data file, samples are separated by blank lines. Each data instance is tokenized and each line contains a single token with the associated label in the last (4th) column. Second and third columns (
_) are ignored. Entities are labeled using the BIO scheme. That means, a token tagged as
O is not part of an entity,
B-X means the token is the first token of an
I-X means the token is in the boundary (but not the first token) of an
X type entity having multiple tokens. In the given example, the input text is:
the original ferrari daytona replica driven by don johnson in miami vice
The following image shows the entities as annotated.
Here are some examples from the other languages.
In this shared task, we provide train/dev/test data for 12 languages. This codalab competition is in practice phase, where you are allowed to submit prediction file for dev sets. The evaluation framework is divided in two broad tracks.
Multi-lingual: In this track, the participants have to train a single multi-lingual NER model using training data for all the languages. This model should be used to generate prediction files for each of the 12 languages’ evaluation (dev/test) set. That means the model should be able to handle monolingual data from any of the languages.
Predictions from any mono-lingual model is not allowed in this track. Therefore, please do not submit predictions from mono-lingual models in this track..
Mono-lingual: In this track, the participants have to train a model that works for only one language. For each language, there will be one dev/test set that contains examples for that particular language. Participants have to train a mono-lingual model for the language of their interest and use that to create prediction file for the evaluation set of that language.
Predictions from any multi-lingual model is not allowed in this track.
4. Submission Instructions
The evaluation script is based on conlleval.pl.
4.1. Format of prediction file
The prediction file should follow CoNLL format but only contain tags. That means, each line contains only the predicted tags of the tokens and sentences are separated by a blank line. Make sure your tags in your prediction file are exactly aligned with the provide dev/test sets. For example,
# id f423a88e-02b7-4d61-a546-4a1bd89cfa15 domain=dev it _ _ _ originally _ _ _ operated _ _ _ seven _ _ _ bus _ _ _ routes _ _ _ which _ _ _ were _ _ _ mainly _ _ _ supermarket _ _ _ routes _ _ _ for _ _ _ asda _ _ _ and _ _ _ tesco _ _ _ . _ _ _ ...
- You will need generate the prediction file
en.pred.conllin the follow format
O O O O O O O O O O O O B-CORP O B-CORP O ...
4.2. Prepare submission files
Follow the below instructions to submit your prediction files for a track. Codalab requires all submissions in zip format
- Use your trained model to generate a prediction file for a specific tack and name it in this format:
- For example, when you participate in the English track, you will need to generate a prediction file for en_dev.conll (or en_test.conll in the testing phase) and name it as en.pred.conll.
- The language_code values for Multilingual track is multi. That means, you will need to name the prediction file as
- Compress the
<language_code>.pred.conllfile to a zip file by using zip
my_submission.zip <language_code>.pred.conll(or your favorite zip utility), and the submit the zip file to the right track on Codalab.
Some Resources for the Beginners in NLP
- Wikipedia article on Named Entity Recognition
- Lecture from Prof. Chris Manning on the Evaluation of Named Entity Recognition
- Named Entity Recognition (NER) using spaCy in Python
- Custom Named Entity Recognition (NER) model with spaCy 3 in Four Steps
- Named Entity Recognition using Transformers with Keras
- Named Entity Recognition Tagging with Pytorch
- How to Fine tune BERT for NER
- Recent SOTA Papers for NER systems in NLP Progress
- Code Switching Leaderboard LinCE.
- Named Entity Recognition on Code-Switched Data: Overview of the CALCS 2018 Shared Task