We invite participation in the competition for text classification of tweets in Urdu. The task is composed of two binary classification subtasks: (A) abusive intent; (B) threatening intent.
text classificationNLPUrdu languageabusive language detectionthreatening language detectiontweet classificationoffensive language detection
This is Subtask B of a double-task competition!
With the growth of spread and importance of social media platforms, the effect of their misuse became more and more impactful. In particular, numerous posts contain abusive language towards certain users and hence worsen users’ experience from communication via such platforms, while other posts contain actual threats that potentially put platform users in danger. The Urdu language has more than 230 million speakers worldwide with vast representation on social networks and digital media.
We encourage participants to propose methods that can automatically detect threat and abuse in Urdu language to avoid violence and outrageous consequences.
Participants may choose to participate in either one or both subtasks. However, to be eligible for the ODS SoC Prize, the participant (participating team) is required to register and submit solutions for both subtasks. Subtask B (Threat detection) is given more weight than Subtask A (abusive language detection). Additionally, publication at FIRE 2021 is strongly encouraged.
Sub-task B focuses on detecting Threatening language using Twitter tweets in Urdu language. This is a binary classification task in which participating systems are required to classify tweets into two classes, namely: Threatening and Non-Threatening.
Threatening - This Twitter post contains any threatening content.
Non-Threatening - This Twitter post does not contain any threatening or profane content.
We followed Twitter's definition to describe Threatening posts toward an individual or groups to threaten with violent acts, to kill or inflict serious physical harm, to intimidate, and to use violent language.
Subtask A is linked here
After the result submission deadline, participants are invited to submit an abstract and a technical report paper with a brief description of their approach and experiments for publication in the FIRE 2021 Proceedings. All the working notes will be published in CEUR Workshop Proceedings. Please, see more information on the publication submission [here]
July 23 – training and test data release; submission platform opens
August 6 - checkpoint at SoC
August 27 - result submission deadline
August 28 - results announced (for the private part of the test set)
September 3-5 - presentations at ODS Summer of Code 2021 festival
October 12 - paper (technical report) submission deadline for publication in Working Notes FIRE 2021 - OPTIONAL, encouraged! (there will be a workshop on academic paper writing)
October 26 - review notifications
November 2 – Camera Ready Due
16-20 December - FIRE 2021 (Online Event)