<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>Hindi-English Code-Mixed Tweets, and Code-Mixed Data Augmentation</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Md Saroar Jahan</string-name>
          <email>mjahan18@edu.oulu.fi</email>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Mourad Oussalah</string-name>
          <email>mourad.oussalah@oulu.fi</email>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Jhuma kabir Mim</string-name>
          <email>Jhuma.mim@student.lut.fi</email>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Mominul Islam</string-name>
          <email>mominul15-11992@diu.edu.bd</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Dafodil International University</institution>
          ,
          <addr-line>Dhaka 1207</addr-line>
          ,
          <country country="BD">BANGLADESH</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>LUT Univerity, Dept of Computational Engineering 53850 Lappeenranta</institution>
          ,
          <country country="FI">FINLAND</country>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>University of Oulu, Faculty of Information Tech., CMVS</institution>
          ,
          <addr-line>PO Box 4500, Oulu 90014</addr-line>
          ,
          <country country="FI">FINLAND</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>The Code-mixed text classification is challenging due to the lack of code-mixed labeled datasets and the non-existence of pre-trained models. This paper presents the HASOC-2021 ofensive language identification results and main findings on code-mixed (Hindi-English) Subtask2. In this work, we have proposed a new method of code-mixed data augmentation using synonym replacement of Hindi and English words using WordNet, and phonetics conversion of Hinglish (Hindi-English) words. We used a 5.7k pre-annotated HASOC-2021 code-mixed dataset for training and data augmentation. The proposal's feasibility was tested with a Logistic Regression (LR) used as a baseline, Convolutional Neural Network (CNN), and BERT with and without data augmentation. The research outcomes were promising and yields almost 3% increase of classifier accuracy and F1 scores as compared to baseline. Our oficial submission showed a 66.56% F1 score and ranked 8th position in the competition.</p>
      </abstract>
      <kwd-group>
        <kwd>Code-mixed Hindi-Englsih</kwd>
        <kwd>Ofensive language identification</kwd>
        <kwd>Code-mixed Data Augmentation</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. Introduction</title>
      <sec id="sec-1-1">
        <title>Social media is a popular and easiest way to express openly and communicate with others online.</title>
      </sec>
      <sec id="sec-1-2">
        <title>Unfortunately, it also provides the means for distributing abusive and aggressive content such as</title>
        <p>
          sexism, racism, politics, cyberbullying, and blackmailing. Nockleby [
          <xref ref-type="bibr" rid="ref1">1</xref>
          ] stated that ’hate speech
disparages a person or group based on some characteristics such as race, color, and ethnicity’.
        </p>
      </sec>
      <sec id="sec-1-3">
        <title>Now its become a challenge; ofensive language is ubiquitous in social media; scholars and</title>
        <p>
          organizations have been focusing on developing an approach that can identify hate speech or
abusive languages and flag them for human restraints or elimination [
          <xref ref-type="bibr" rid="ref2">2</xref>
          ]. Prior work has studied
ofensive language detection in Twitter [
          <xref ref-type="bibr" rid="ref3 ref4">3, 4, 5</xref>
          ], Wikipedia comments and Facebook posts [6],
        </p>
      </sec>
      <sec id="sec-1-4">
        <title>FromSpring posts [7], youtube Dinakar et al.[8], News article [9] and AskFm post [5, 10].</title>
      </sec>
      <sec id="sec-1-5">
        <title>However, the challenges become critical when social posts are written with Code-Mixed (CM) language. The Code-mixing, which is the phenomenon of mixing words from two languages</title>
        <p>in a sentence, is getting increasingly commonplace in several bilingual communities, which
renders the automatic making detection task more challenging [11].</p>
        <p>Many works focused on deep learning-based models to identify the aggressive language in
social media texts. For instance, Agrawal and Awekar[12] investigated how learning-based
models can capture more dispersed features on various platforms and topics. Bu and Cho[13]
provided a hybrid deep learning model that combines CNN and Long-term Recurrent
Convolutional Networks (LRCN) to detect ofensive in Social Networking Service (SNS) comments. A
character-level CNN model with shortcuts was proposed by Lu et al. [14]. In addition, Rosa
et al.[15] compared three diferent deep learning approaches, trained from three diferent sources
for multiple category textual ofensive detection.</p>
      </sec>
      <sec id="sec-1-6">
        <title>The Natural Language Processing (NLP) community organized several initiatives and seminars</title>
        <p>to cope with the scenarios above to stimulate research on hateful speech and ofensive content
in social media, such as Semeval-2019[16] and 2020[17], HASOC-2019 [18] and 2020[19]. From
previous work, BERT model outperformed most of other state-of-the-art models. The rise of</p>
      </sec>
      <sec id="sec-1-7">
        <title>BERT is a striking trend that testifies of its popularity in the hate speech detection community (38% share of deep-learning models) in the past five years [ 20]</title>
      </sec>
      <sec id="sec-1-8">
        <title>In this year, 2021, for the first time, HASOC provides Subtask2[ 21], which ofers a multilingual</title>
        <p>ofensive code-mixed language identification task in social media-Twitter. In this contest, our
team participated to SubTask2 for Hindi-English code-mixed identification of Hate/ofensive
Tweets. We have used the HASOC-2021 shared dataset for training and validation. Since
the absence of large-scale code-mixed labeled corpus, an intuitive approach is to seek an
appropriate data augmentation strategy. It is challenging to obtain universal transformation
rules in natural languages that assure the quality of the produced data and easy automated
application procedures in various domains. A common approach for a such a transformation is
to replace words with their synonyms selected from a handcrafted ontology such as WordNet
[22]. Another synonym replacement approach is based on pre-trained word embeddings such
as GloVe, FastText, Sent2Vec, etc. The nearest neighbor words in the embedding space are a
replacement for some word in the sentence or word similarity calculation [23]. Back-translation
and paraphrasing augmentation also shown higher accuracy for supervised learning [24]. A
recent trend is contextual data augmentation that stochastically replaces words with other words
predicted by a bi-directional language model at the corresponding word positions. However,
code-mixed datasets are an amalgamation of multilingual tokens, making them limited to
existing augmentation methods. For example, contextual augmentation with the transformer
model requires pre-trained models, and to the best of our knowledge, pre-trained models for
codemixed are still scarce. Furthermore, many tokes are written native phonetically but in a diferent
language; therefore, it is impossible to use synonym replacement without further conversion.
We focused on code-mixed data augmentation to overcome these challenges by using synonym
replacement with WordNet, phonetics conversion, translation, and back-translation for relevant
tweets. The paper posits some main contributions as follow:
• A data augmentation scheme has been put forward that has not been experimented for
code-mixed dataset.
• We developed a new python library for data augmentation, which is the end product of
our experiment, and would be released under an open-sourced license for the research
community 1.
• We constructed a newly extended code-mixed (Hindi-English) dataset and released it
publicly.</p>
        <p>The paper is structured as follows. Section 2 describes our methodology, consisting of dataset
annotation schema, preprocessing, dataset augmentation, and classifier architectures, including
the machine learning models and the associated feature engineering. Section 3 details and
comments on our experimental result. In Section 4, an error analysis task of our best models is
performed. Finally, conclusive statements and potential future work are drawn in the conclusion
section.</p>
      </sec>
    </sec>
    <sec id="sec-2">
      <title>2. Methodology</title>
      <sec id="sec-2-1">
        <title>The overall experimentation methodology includes a four-stage process: (i) data collection and preprocessing, (ii) Code-mix data augmentation, (iii) ML model setup, (iv) results comparison before and after augmentation, and (iv) error analysis.</title>
      </sec>
      <sec id="sec-2-2">
        <title>The experiment environment will be the same for all experiments (e.g., data preprocessing, data augmentation, machine learning (ML) architecture, test data, and error analysis).</title>
        <sec id="sec-2-2-1">
          <title>2.1. Datasets</title>
        </sec>
      </sec>
      <sec id="sec-2-3">
        <title>To train our models and compare our results, we used the Code-mixed twitter dataset from</title>
      </sec>
      <sec id="sec-2-4">
        <title>HASOC-2021. The dataset tweet consists of eight diferent controversial topics: (i) Twitter</title>
      </sec>
      <sec id="sec-2-5">
        <title>Conflicts with the Indian Government on new IT rules. (ii) Casteism controversy in India (ii)</title>
      </sec>
      <sec id="sec-2-6">
        <title>Charlie Hebdo posts on Hinduism (iv ) The Covid-19 crisis in India 2021 (v) Indian Politics</title>
        <p>(vi)The Israel-Palestine conflict in 2021 (vii) Religious controversies in India and (viii) The
coronavirus controversy.</p>
        <p>The HASOC task organizer already annotated datasets for Subtask2. For hate/ofensive posts,
it is labeled as HOF, and for non-hate/ofensive, it is labeled as NONE. The Code-mixed dataset
consists of approximately 5740 training data from Twitter tweets, re-tweets, comments, and
replies; among 2841(45%) are ofensive, and 2899(55%) are not-ofensive. Table 1 shows the
example of annotated code-mixed.</p>
      </sec>
      <sec id="sec-2-7">
        <title>1. (NONE) Non-Hate/Ofensive - This post does not contain any Hate speech, profane,</title>
        <p>ofensive content.</p>
      </sec>
      <sec id="sec-2-8">
        <title>2. (HOF) Hate and Ofensive - This post contains Hate, ofensive, and profane content.</title>
      </sec>
      <sec id="sec-2-9">
        <title>1. Hindi Token: Hindi words written in Hindi letter.</title>
        <p>1https://pypi.org/project/nlp-augment/</p>
      </sec>
      <sec id="sec-2-10">
        <title>2. English token: English words written in English letter.</title>
      </sec>
      <sec id="sec-2-11">
        <title>3. Phonetic Hinglish token: Hindi word written phonetically in English letter.</title>
      </sec>
      <sec id="sec-2-12">
        <title>Four diferent types of posts/sentence formation are as follow (e.g., posts Table 1):</title>
      </sec>
      <sec id="sec-2-13">
        <title>1. Hindi posts consist of Hindi tokens,</title>
      </sec>
      <sec id="sec-2-14">
        <title>2. English posts consist of English tokens,</title>
      </sec>
      <sec id="sec-2-15">
        <title>3. Phonetic Hindi posts consist of the phonetic Hinglish tokens, and</title>
      </sec>
      <sec id="sec-2-16">
        <title>4. Posts mixture of three types of tokens.</title>
        <p>The second challenge of Subtask2 is related to its unique annotation criteria. For example,
each tweet in the dataset could have a conversational thread that may contain hate and ofensive
content, which is not apparent just from a single comment or the reply to a comment but can
be identified if given the context of the parent content. Table 2 shows relational annotation; for
example, the comment’s reply ’You totally nailed it, can’t stop laughing’ seems not ofensive;
however, since it is supporting the original post, which was ofensive, therefore it becomes
ofensive as well.</p>
        <p>You totally nailed it, can’t stop laughing</p>
        <p>Translation
They have asked Doctors
and Scientists. Not fuckers.</p>
        <p>Sit down.</p>
        <p>Label
HOF
HOF
2.1.1. Data Preprocessing</p>
      </sec>
      <sec id="sec-2-17">
        <title>We have eliminated special characters, numeric values (e.g., @,0-9), newlines, mention tags, and URLs for data preprocessing. We have not removed hashtags since we have found them important. Table 3 shows example tweets before and after preprocessing.</title>
        <p>#resignmodi kon chutiya ka
interview liye ho
Translation of Source
posts
who make him dog
Who has interviewed
fucker?</p>
        <sec id="sec-2-17-1">
          <title>2.2. Code-mixed Data Augmentation</title>
          <p>As discussed in Section 2.1, the dataset has three diferent types of tokens that have formed four
diferent kinds of posts. Our proposed augmentation methods are followed by three diferent
kinds of approaches that have been employed to cover all types of tokens and posts. For example,
if posts consist of all 3 types of tokens, it is impossible to translate the sentence and reform it as
a meaningful sentence. In that case, each token was targeted individually and identified by its
type for further processing. For Hindi/English token, it is replaced by its synonyms. However, if
the token was phonetics, it is converted to Hindi word using python library2; finally, synonym
replacement is performed. After each token conversion, we have restored the sentence with
2https://pypi.org/project/pyhinavrophonetic/
diferent types of the augmented token. Figure 1 shows the token-based augmentation and
reformation of new posts.</p>
        </sec>
      </sec>
      <sec id="sec-2-18">
        <title>If posts/sentences contain more than 90% token where all of them are either Hindi or English, a translation, back-translation, and Hindi phonetics conversion have been applied to the whole posts altogether. Figure 2 exhibits an example of translation, back-translation and phonetics conversion of posts.</title>
      </sec>
      <sec id="sec-2-19">
        <title>1. Posts that contain more than 90% of English token: three types of augmentation strategies</title>
        <p>were performed (i) English to Hindi translation, (ii) Hindi to a phonetics, written in</p>
      </sec>
      <sec id="sec-2-20">
        <title>English but pronounced as Hindi, and (iii) Hindi to Bagla and back-translated to English</title>
        <p>again.</p>
      </sec>
      <sec id="sec-2-21">
        <title>2. Similarly, posts that contain more than 90% Hindi token: three types of augmentation</title>
        <p>performed (i) Hindi to English translation, (ii) Hindi to phonetic, and (iii) Back-translation,</p>
      </sec>
      <sec id="sec-2-22">
        <title>Hindi to Bangla to Hindi .</title>
      </sec>
      <sec id="sec-2-23">
        <title>Finally, both word-level and post-level augmentation were saved to CSV files containing 132k augmented sentences, which were 23.8 times larger than non-augmented ones.</title>
        <sec id="sec-2-23-1">
          <title>2.3. Classifier architecture</title>
        </sec>
      </sec>
      <sec id="sec-2-24">
        <title>Initially, we employed a random split of the original dataset into 80% for training and 20% for</title>
        <p>testing and validation, ensuring the same proportion of dataset for all kinds of model learning.</p>
      </sec>
      <sec id="sec-2-25">
        <title>Three classifiers were implemented for training and testing: Logistics regression (LR) with</title>
        <p>word-level TF-IDF, Convolution Neural Network (CNN) with word-level TF-IDF, and fine-tuned</p>
      </sec>
      <sec id="sec-2-26">
        <title>BERT pre-trained model. During the experiment, the test data has not been changed for both augmented and non-augmented datasets.</title>
        <p>Where is the mask
मुर्ख
chuthiye
Where is the mask
&lt;fool&gt; &lt;pussy&gt;
Where is the &lt;cover&gt;
मुर्ख
chuthiye
Where is the mask
&lt;idiot&gt; chuthiye
Sentence level Aug. Augmentation steps
Fugitive son of a cow- Eng. &gt; Hi. &gt; Eng. BT.
ard
Bhagode Kaayar ka Eng. &gt; Hi. &gt; Phonetics
beta
Sale bhagode Kaayar Eng. &gt; Hi. &gt; Phonetics
ka beta
भगोड़े कायर का बेटा Eng. &gt;Hi. translation
Hi. &gt; Eng, Phonetic &gt;
Hi. &gt; Eng.</p>
        <p>Eng. synonym (mask &gt;
cover)
Hi. &gt; Eng.</p>
        <sec id="sec-2-26-1">
          <title>2.4. Experiment Setup CNN</title>
          <p>We adopted [25] a CNN, architecture, where the input layer is represented by a concatenation
of the words forming the post (up to 70 words), except that each word is now a TF-IDF vector
representation. Though several experiments showed using word embedding (e.g., fastText)
performed better when used with CNN in the embedding layer[20]; however, no available
pretrained word embedding was found for code-mixed Hindi-English. A convolution 1D operation
with a kernel size 3 was used together with a max-over-time pooling operation over the feature
map with a layer dense 50. Dropout on the penultimate layer with a constraint on 12-norms of
the weight vector was used for regularization.</p>
        </sec>
      </sec>
      <sec id="sec-2-27">
        <title>The details of the implementation are reported on our GitHub page of this project with</title>
        <p>datasets and codes3.</p>
        <sec id="sec-2-27-1">
          <title>2.5. Transformer model</title>
          <p>BERT – Bidirectional Encoder Representations from Transformers: this seminal
transformerbased language model employs an attention mechanism that enables the mode to learn contextual
relations between (sub-)words in a text sequence [26]. BERT uses two training strategies:</p>
        </sec>
      </sec>
      <sec id="sec-2-28">
        <title>1. MLM: where 15 % of the tokens in a sequence are replaced (masked) for which the model</title>
        <p>learns to predict the original tokens, and</p>
      </sec>
      <sec id="sec-2-29">
        <title>2. NSP where the model receives pairs of sentences as input and learns to predict whether or not the second sentence is a successor of the first one in their original document context.</title>
        <sec id="sec-2-29-1">
          <title>2.6. Experiemnt setup with BERT model</title>
        </sec>
      </sec>
      <sec id="sec-2-30">
        <title>We fine-tuned diferent transformer models with the HASOC-2021 training data using the</title>
        <p>corresponding test data for validation. The following models were tested: BERT-base (uncased)
and BERT-multilingual. Each model was fine-tuned for 6 epochs with a learning rate of 5e-6,
maximum sequence length of 128, and batch size 4. After each epoch, the model was evaluated
on the validation set.</p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>3. Results</title>
      <p>3https://github.com/saroarjahan/Hasoc_2021_subtask2 (accessed September 20, 2021)
and BERT-multilingual. The results exhibit model accuracy and F1 scores for both augmented
and non-augmented dataset for comparison. In both cases, we see that CNN with word-level
TF</p>
      <sec id="sec-3-1">
        <title>IDF largely outperform baseline LR. Comparing BERT and CNN model reveals that CNN model</title>
        <p>slightly (.5%) outperform both BERT-base-uncased and BERT-multilingual. It is unusual that
CNN showed much better performance compared to BERT models. The possible explanation is
that we need a pre-trained model that would reflect our dataset; however, no pre-trained models
were found that can be useful for code-mixed. Though BERT multilingual was trained with 104
languages; however, the BERT-multilingual model has not outperformed CNN. This agreed with
our intuition since the multilingual pre-trained model was trained on the top 104 languages
with the largest Wikipedia using a masked language modeling (MLM) objective; however, it
contains only a small percentage of English and Hindi tokens. Therefore, it might have fallen
short as the HASOC-2021 code-mixed dataset is related to Hindi, English, and amalgamation of
phonetics tokens.</p>
      </sec>
      <sec id="sec-3-2">
        <title>Our data augmentation results showed success since it has shown a better performance in all</title>
        <p>models. After using data augmentation for model training, it resulted in almost 3% increase
compared to the non-expanded dataset. This improvement has been shown for baseline, CNN,
and BERT models. Since we have kept the experiment test dataset identical for all models, this
improvement justifies the proposed augmentation method that has helped the model to train
better.</p>
      </sec>
      <sec id="sec-3-3">
        <title>We have submitted our best performing model (CNN) results to the HASOC-21 competition, and an oficial result [ 27], we have received was 66.56% F1 score (Table 7).</title>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>4. Error Analysis</title>
      <sec id="sec-4-1">
        <title>Our final submission F1 macro score was 66.56%, which has outperformed most submissions;</title>
        <p>however, the F1 score seems low, which indicates the model exhibits a large portion of false
detection. We performed in this section an analysis of the model’s performance and train dataset
evaluation to understand this phenomenon better. For this purpose, we randomly prepared 200
subsets of test data then manually inspected each annotation.</p>
        <p>From Figure 3, we see that 232 of the error is related to false-negative (FN), and 421 hate
samples were correctly identified. In contrast, 477 non-hate samples were correctly detected,
and 218 resulted as false positive (FP). This indicates that our model was not performing as good
as detecting non-hate samples. Since our train dataset in its majority (55%) contains non-hate
samples, it seems our model is better trained or biased towards non-hate classes. Another
possible explanation of the overall model’s low performance is due to the fact that errors might
be coming from the training samples. For example, our manual inspection of 200 samples
showed that 4% of the test sample was annotated wrongly (Table 4). Since this test data was a
split of original data, the wrong annotation of test data raises the question of overall training
data quality, which might have afected model training. Furthermore, the training data were
mostly relational data of tweets, retweets, comments, and replies. Therefore a single post was
an amalgamation of hate and not-hate samples, which made the classifier dificult to train.</p>
      </sec>
    </sec>
    <sec id="sec-5">
      <title>5. Conclusion</title>
      <sec id="sec-5-1">
        <title>In the HASOC-2021 competition, we have worked on Code-Mixed (Hindi-English) dataset</title>
        <p>Subtask2 for hate-ofensive post identification. We performed diferent experiments of twitter
preprocessing, classification with LR, CNN, and BERT-finetuned models. Our tweet
preprocessing showed removing the mentioned tag and removing special characters and URLs were
useful and yield an increased of almost 1% in classification accuracy. However, eliminating
hashtags and stemming reduced the overall performance. This provides a basis for optimal
preprocessing pipeline. For classification purpose, we proposed a data augmentation strategy
for code-mix dataset. Since the code-mixed dataset is a combination of Hindi, English, and
HingLish tokens, we applied data augmentation that employs WordNet synonym replacement,
conversation phonetics to Hindi, translation, and back-translation of sentences. After training
with the augmented dataset, all models showed an approximate 3% improvement in classification
accuracy and F1 accuracy. Among BERT and CNN, CNN performed little better than BERT
models since there was no available pre-trained model for the code-mix dataset. Our best
test CNN models showed 69.6 F1 scores, and the oficial submission result showed 66.65% f1
scores. In the future, it would be interesting to experiment with contextual augmentation using</p>
      </sec>
      <sec id="sec-5-2">
        <title>Code-Mixed pre-trained model.</title>
        <p>Picking up any matter, come with casting the cast, now
stop, it is not India of 1947, 2021 has come, now leave
this thing
watch video randeep hooda make dirti joke nation leader
mayavati dalit woman voic oppress toler castiest peopl
arrest #arresterandeephood chup teri ka bsda
watch video randeep hooda make dirti joke nation leader
mayavati dalit woman voic oppress toler castiest peopl
arrest #arresterandeephood chup kar saal ka baccha joke
funni
watch video randeep hooda make dirti joke nation leader
mayavati dalit woman voic oppress toler castiest peopl
arrest #arresterandeephood Supper
watch video randeep hooda make dirti joke nation leader
mayavati dalit woman voic oppress toler castiest peopl
arrest #arresterandeephood The show should be cancelled
watch video randeep hooda make dirti joke nation leader
mayavati dalit woman voic oppress toler castiest peopl
arrest #arresterandeephood God is Ram Rahim for you,
now we don’t expect you to use your brain
Original La- label should
bel be
HOF NONE
HOF
NONE
HOF
HOF
NONE</p>
        <p>HOF
NONE
NONE
HOF</p>
      </sec>
    </sec>
    <sec id="sec-6">
      <title>6. Acknowledgments</title>
      <sec id="sec-6-1">
        <title>We would like to thank the HASOC-2021 sharing task organizers for giving us the opportunity to submit this work. Secondly, this project was partially funded by EU Project WaterLine (Downscaling Remotely Sensed Products to Improve Hydrological Modelling Performance), which is gratefully acknowledged.</title>
        <p>[5] Y. J. Foong, M. Oussalah, Cyberbullying system detection and analysis, in: 2017 European</p>
      </sec>
      <sec id="sec-6-2">
        <title>Intelligence and Security Informatics Conference (EISIC), IEEE, 2017, pp. 40–46.</title>
        <p>[6] R. Kumar, A. K. Ojha, S. Malmasi, M. Zampieri, Benchmarking aggression identification
in social media, in: Proceedings of the First Workshop on Trolling, Aggression and
Cyberbullying (TRAC-2018), 2018, pp. 1–11.
[7] K. Reynolds, A. Kontostathis, L. Edwards, Using machine learning to detect
cyberbullying, in: 2011 10th International Conference on Machine learning and applications and
workshops, volume 2, IEEE, 2011, pp. 241–244.
[8] K. Dinakar, B. Jones, C. Havasi, H. Lieberman, R. Picard, Common sense reasoning for
detection, prevention, and mitigation of cyberbullying, ACM Transactions on Interactive
Intelligent Systems (TiiS) 2 (2012) 1–30.
[9] Y. Bounab, J. M. Adeegbe, M. Oussalah, Towards storytelling automatic textual summerized,
in: Conference of Open Innovations Association, FRUCT, 25, FRUCT Oy, 2019, pp. 434–438.
[10] M. S. Jahan, O. Mourad, Team oulu at semeval-2020 task 12: Multilingual identification of
ofensive language, type and target of twitter post using translated datasets, in: Proceedings
of the Fourteenth Workshop on Semantic Evaluation, 2020, pp. 1628–1637.
[11] I. A. Bhat, V. Mujadia, A. Tammewar, R. A. Bhat, M. Shrivastava, Iiit-h system submission for
ifre2014 shared task on transliterated search, in: Proceedings of the Forum for Information</p>
      </sec>
      <sec id="sec-6-3">
        <title>Retrieval Evaluation, 2014, pp. 48–53.</title>
        <p>[12] S. Agrawal, A. Awekar, Deep learning for detecting cyberbullying across multiple social
media platforms, in: European Conference on Information Retrieval, Springer, 2018, pp.
141–153.
[13] S.-J. Bu, S.-B. Cho, A hybrid deep learning system of cnn and lrcn to detect cyberbullying
from sns comments, in: International Conference on Hybrid Artificial Intelligence Systems,
Springer, 2018, pp. 561–572.
[14] N. Lu, G. Wu, Z. Zhang, Y. Zheng, Y. Ren, K.-K. R. Choo, Cyberbullying detection in
social media text based on character-level convolutional neural network with shortcuts,</p>
      </sec>
      <sec id="sec-6-4">
        <title>Concurrency and Computation: Practice and Experience (2020) e5627.</title>
        <p>[15] H. Rosa, D. Matos, R. Ribeiro, L. Coheur, J. P. Carvalho, A “deeper” look at detecting
cyberbullying in social networks, in: 2018 International Joint Conference on Neural
Networks (IJCNN), IEEE, 2018, pp. 1–8.
[16] M. Zampieri, S. Malmasi, P. Nakov, S. Rosenthal, N. Farra, R. Kumar, Semeval-2019 task 6:
Identifying and categorizing ofensive language in social media (ofenseval), arXiv preprint
arXiv:1903.08983 (2019).
[17] M. Zampieri, P. Nakov, S. Rosenthal, P. Atanasova, G. Karadzhov, H. Mubarak, L.
Derczynski, Z. Pitenis, Ç. Çöltekin, Semeval-2020 task 12: Multilingual ofensive language
identification in social media (ofenseval 2020), arXiv preprint arXiv:2006.07235 (2020).
[18] T. Mandl, S. Modha, P. Majumder, D. Patel, M. Dave, C. Mandlia, A. Patel, Overview of the
hasoc track at fire 2019: Hate speech and ofensive content identification in indo-european
languages, in: Proceedings of the 11th forum for information retrieval evaluation, 2019,
pp. 14–17.
[19] T. Mandl, S. Modha, A. Kumar M, B. R. Chakravarthi, Overview of the hasoc track at
ifre 2020: Hate speech and ofensive language identification in tamil, malayalam, hindi,
english and german, in: Forum for Information Retrieval Evaluation, 2020, pp. 29–32.
[20] M. S. Jahan, M. Oussalah, A systematic review of hate speech automatic detection using
natural language processing, arXiv preprint arXiv:2106.00742 (2021).
[21] S. Satapara, S. Modha, T. Mandl, H. Madhu, P. Majumder, Overview of the HASOC</p>
      </sec>
      <sec id="sec-6-5">
        <title>Subtrack at FIRE 2021: Conversational Hate Speech Detection in Code-mixed language ,</title>
        <p>in: Working Notes of FIRE 2021 - Forum for Information Retrieval Evaluation, CEUR, 2021.
[22] X. Zhang, J. Zhao, Y. LeCun, Character-level convolutional networks for text classification,</p>
        <p>Advances in neural information processing systems 28 (2015) 649–657.
[23] S. Wang, J. Liu, X. Ouyang, Y. Sun, Galileo at semeval-2020 task 12: Multi-lingual learning
for ofensive language identification using pre-trained language models, arXiv preprint
arXiv:2010.03542 (2020).
[24] D. R. Beddiar, M. S. Jahan, M. Oussalah, Data expansion using back translation and
paraphrasing for hate speech detection, Online Social Networks and Media 24 (2021)
100153.
[25] Y. Kim, Convolutional neural networks for sentence classification, arXiv preprint
arXiv:1408.5882 (2014).
[26] J. Devlin, M.-W. Chang, K. Lee, K. Toutanova, Bert: Pre-training of deep bidirectional
transformers for language understanding, arXiv preprint arXiv:1810.04805 (2018).
[27] S. Modha, T. Mandl, G. K. Shahi, H. Madhu, S. Satapara, T. Ranasinghe, M. Zampieri,</p>
      </sec>
      <sec id="sec-6-6">
        <title>Overview of the hasoc subtrack at fire 2021: Hate speech and ofensive content identi</title>
        <p>ifcation in english and indo-aryan languages and conversational hate speech, in: FIRE
2021: Forum for Information Retrieval Evaluation, Virtual Event, 13th-17th December
2021, ACM, 2021.</p>
      </sec>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>J. T.</given-names>
            <surname>Nockleby</surname>
          </string-name>
          , Hate speech,
          <source>Encyclopedia of the American constitution 3</source>
          (
          <year>2000</year>
          )
          <fpage>1277</fpage>
          -
          <lpage>1279</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>J.</given-names>
            <surname>Risch</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Krestel</surname>
          </string-name>
          ,
          <article-title>Delete or not delete? semi-automatic comment moderation for the newsroom</article-title>
          ,
          <source>in: Proceedings of the first workshop on trolling, aggression and cyberbullying (TRAC-2018)</source>
          ,
          <year>2018</year>
          , pp.
          <fpage>166</fpage>
          -
          <lpage>176</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>P.</given-names>
            <surname>Burnap</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M. L.</given-names>
            <surname>Williams</surname>
          </string-name>
          ,
          <article-title>Cyber hate speech on twitter: An application of machine classification and statistical modeling for policy and decision making</article-title>
          ,
          <source>Policy &amp; Internet</source>
          <volume>7</volume>
          (
          <year>2015</year>
          )
          <fpage>223</fpage>
          -
          <lpage>242</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>M.</given-names>
            <surname>Wiegand</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Siegel</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Ruppenhofer</surname>
          </string-name>
          ,
          <article-title>Overview of the germeval 2018 shared task on the identification of ofensive language (</article-title>
          <year>2018</year>
          ).
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>