<!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>
      <journal-title-group>
        <journal-title>Forum for Information Retrieval Evaluation, December</journal-title>
      </journal-title-group>
    </journal-meta>
    <article-meta>
      <title-group>
        <article-title>Detection using LIME guided Ensemble Method and DistilBERT</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>N Deepakindresh</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>AviReddy Rohan</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Aakash Ambalavanan</string-name>
          <email>aakash.ambalavanan2019@vitstudent.ac.in</email>
          <xref ref-type="aff" rid="aff1">1</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>B. Radhika Selvamani</string-name>
          <email>radhika.selvamani@vit.ac.in</email>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>DistilBERT</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>(B. R. Selvamani)</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Center for Advanced Data Science, Vellore Institute of Technology</institution>
          ,
          <addr-line>Chennai</addr-line>
          ,
          <country country="IN">India</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Hate Speech Identification, TF-IDF</institution>
          ,
          <addr-line>Ensemble, LSTM, SVM, Random Forest, Logistic Regression, LIME</addr-line>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>Vellore Institute of Technology</institution>
          ,
          <addr-line>Chennai</addr-line>
          ,
          <country country="IN">India</country>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2021</year>
      </pub-date>
      <volume>1</volume>
      <fpage>3</fpage>
      <lpage>17</lpage>
      <abstract>
        <p>Hate Speech classification has crucial applications in the social media domain. We describe the performance of our classifiers in the Hate Speech and Ofensive Content Identification Track (HASOC) of FIRE 2021 conference. The dataset provided is for Indo-European Languages. We chose English tweets and developed two main classifiers as part of HASOC Track 1, which had two Subtasks 1A and 1B. Subtask 1A is a binary Hate Speech identification task, and Subtask 1B is multi grained classification of hate, profane, ofensive and neutral content. Our team ”Beware Haters” studied Support Vector Machine, Random Forest, Logistic Regression, Bidirectional Long Short Term Memory Model and an Ensemble of the listed models for the Subtask 1A and the highest Macro F1 score we achieved was 0.7722 by our Ensemble model which combined the advantages of SVM, Logistic Regression and Random Forest. We used a model interpretation tool LIME, before integrating the models in a weighted Ensemble approach. For Subtask 1B, we obtained better results using a DistilBERT model that achieved a Macro F1 score of 0.6311. We have compared the performance of the basic DistilBERT Model with a fine tuned version.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. Introduction</title>
      <p>
        The initial research in hate speech dates back to 1993 and has been legally defined by John
T. Nockleby to describe any communication that incites hatred against anyone or any group
of people in the name of race, ethnicity, religion, sexual orientation etc [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. Hate speech
identification task caught up with the Machine learning community during the spurt of user
created content in social media during the last decade. Huge eforts have been put forth in
the task of hate speech identification on the internet by Facebook [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ], Twitter and Youtube,
to conform to the legal and social responsibilities posed on these sites through governmental
policies. Meanwhile, the research community finds the task of hate speech identification to be
challenging, due to the diversity of the hate speech statements and the skewed nature of the
collected data in most websites. Hate speech also poses challenges concerning the language
used and the context in which it originates [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]. These challenges have made the hate speech
identification task an interesting topic to be studied in the light of new machine learning
algorithms and approaches which have been made available by cloud based libraries. The first
HASOC Track of workshops created annotated hate speech in Indo-European languages to
enable continued research in this direction. A detailed explanation about the HASOC Track at
FIRE 2019 conference and the datasets have been discussed by Mandl et al.,2019 [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]. This paper
is a summary of the eforts put forth by our team Beware Haters in the HASOC 2021 Track 1 [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ].
There were multiple tracks analysing Twitter tweets in diferent code-mixed languages. We
participated in the English hate speech identification subtasks of Track 1 [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]. There were two
diferent subtasks in Track 1. The Subtask 1A requires the participants to identify hate speech
in the given tweets and Subtask 1B is about classifying the tweets into multiple classes such as
Hate, Profane, Ofensive, Neutral etc.
      </p>
    </sec>
    <sec id="sec-2">
      <title>2. Dataset Analysis</title>
      <p>The dataset that we chose for analysis consisted only of English tweets. We analysed two
diferent Subtasks 1A and 1B of Track 1. Subtask 1A is a binary classification task on tweets
belonging to two distinct categories namely HOF (Hate and Ofensive) and NOT (Non
HateOfensive). HOF consists of hateful, ofensive and profane content whereas NOT represents
neutral content. Subtask 1B is a fine-grained classification problem, with 4 distinct classes,
namely hate, ofensive, profane and neutral (usually represented as none). The size of the dataset
including training and test data is limited to about 4000 tweets. To overcome the data limitation
we collected additional data from other sources. A free and publicly available Twitter hate
speech dataset from Kaggle1 was chosen for data augmentation and solving the class imbalance
problem in the dataset provided by HASOC. On manual scrutiny, we found substantial similarity
between the HASOC and Kaggle datasets for Subtask 1A. This Kaggle dataset has approximately
six thousand tweets with labels comparable to HOF and NOT. The HASOC training dataset
contains 65% HOF tweets whereas the Kaggle dataset consists of only 45% HOF tweets [Fig.1].
The combined dataset has 40% of HASOC data and 60% of Kaggle data and was used for the
Random Forest model and Ensemble model for Subtask 1A. The dataset provided by HASOC for
ifne-grained classification of English tweets (Subtask 1B of HASOC 2021 Track 1) has 18% hate,
16% ofensive, and 31% profane tweets [Fig. 2]. We did not use any additional data for Subtask
1B other than the dataset provided by the HASOC 2021 organizers.</p>
    </sec>
    <sec id="sec-3">
      <title>3. Feature Engineering</title>
      <p>We extensively analysed the tweets from the dataset to decide on the pre-processing step. Tweets
have been either removed or have been transformed using pattern matching techniques to deem
them fit to the classification models under consideration. We have filtered out non-informative
features from the tweets like URLs, white spaces, usernames that start with @ and hashtags.
Other features like emojis have been filtered out. The tweets have been decontracted. Words
1https://www.kaggle.com/vkrahul/twitter-hate-speech
like won’t, don’t, can’t, he’ll, I’ll etc have been converted to their complete forms. Stop words
are those that appear very frequently in the tweets but don’t help in conveying any meaning.
Common stop words like the, not, is and was have been removed. In addition, we have performed
tokenization and lemmatization of the preprocessed tweets. Table 1 shows some examples of
tweets before and after preprocessing.</p>
      <p>Before preprocessing
@krtoprak_yigit Soldier of Japan Who has dick head
@blueheartedly You’d be better of asking who DOESN’T
think he’s a sleazy shitbag lmao.
@wealth if you made it through this &amp;amp;&amp;amp; were
not only able to start making money for yourself but
sustain living that way all from home, fuck these
companies &amp;amp; corporate pigs. power to the people,
always.</p>
      <p>Technically that’s still turning back the clock, dick head
https://t.co/jbKaPJmpt1
After preprocessing
soldier japan dick head
would better ask think sleazy
shitbag lmao
make not able start make money sustain
live way home fuck company corporate pig
power people always
technically still turn back clock dick head</p>
      <p>
        A word embedding is a fixed length floating point vector whose length may be pre-specified.
Word embedding approaches transform the uneven text statements to eficient dense numerical
vector representation of fixed length. Our benchmark algorithm used feature engineering
techniques of n-grams with tf-idf vectorization [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ] to convert words into vectors of size 3843
[Fig.3].
      </p>
      <p>We have compared the performance of tf-idf vectorization to the native word2vec embedding
of TensorFlow, where words are represented in an n-dimensional vector space in such a way
that words are clustered based on their semantic similarity. [Fig.3] shows the feature space of
the tf-idf approach after removing the stop words. Since we were restricted with very little data,
we used a 32-dimensional word2vec embedding for the Bidirectional LSTM, a sequence classifier
that captures contextual information from a sequence. The vectors obtained were plotted using
the embedding projector provided by TensorFlow. The visualizations were useful to validate the
vectorization approach, that categorizes semantically similar words to the same cluster. The plot
in [Fig.4] was obtained by applying the Principal Component Analysis method on the word2vec
vector space for dimension reduction. The result is plotted in 3D by spherizing the data. We
visualized that the spherized word vectors of similar words such as idiot and uneducated were
closer to each other [Fig.4] in the 3D plot. By configuring the T-SNE (T-distributed Stochastic
Neighbour Embedding) with a perplexity measure of 25 and a learning rate of 10 we obtained a
2d plot as shown in [Fig.5]. The [Fig.5] has a visualization of the T-SNE word embedding after
2500 iterations. The words rape and rapers are present in the top cluster but the word grape,
which rhymes with rape has been correctly classified into the bottom cluster.</p>
      <p>The PCA plot and T-SNE plot have been visualized for the words fuck [Fig.6], ass [Fig.7]
and bjp [Fig.8] respectively. The word ass seems to be associated with other semantically
similar words such as harass, embarrass etc. But compassion seems to be wrongly grouped in
along with the above words. The word bjp has been associated with most political phrases
irrespective of the polarity of the sentiments. We observe that the word2vec approach used
clusters semantically similar words in an acceptable manner.</p>
    </sec>
    <sec id="sec-4">
      <title>4. The Hate Speech Identification Task</title>
      <p>
        Hate speech identification has been perceived as a binary classification problem to determine
whether a twitter content is hateful-ofensive or not. We compared the performance of various
binary text classifiers on the training data. We used an n-gram based tf-idf vector embedding to
prepare the training data used for learning the models. Logistic Regression [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ] is a well-known
simple regression model that serves as a basic model for binary classification. Random Forest is a
widely used meta estimator that fits a number of decision tree classifiers on various sub-samples
of the dataset and uses averaging to improve the predictive accuracy and control over-fitting [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ].
The number of estimators and the sub-sample size for each estimator are some of the parameters
used to fine tune the approach. We used 2000 estimators and a minimum sample-size of 2
per estimator as per the default settings of sklearn’s Random Forest Classifier. The Support
Vector Machine [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ] is a state-of-the-art machine learning model with proven performance in
countless machine learning applications with sparse high dimensional data. It uses diferent
kernels, namely Linear, polynomial, Radial basis function, and sigmoid to transform the data to
a lower dimension, which enables application of maximum margin classifier for obtaining the
decision plane.
      </p>
      <sec id="sec-4-1">
        <title>4.1. Sequence Classifiers</title>
        <p>
          In addition to the simple classifiers listed above, we have explored sequence classifiers using
Long Short-Term Memory Models (LSTM) [
          <xref ref-type="bibr" rid="ref11">11</xref>
          ]. LSTM is a kind of Recurrent Neural Network
(RNN) model, which has the added benefit of encoding contextual meaning among the words
for a longer time step. Bidirectional LSTMs overcome the directional bias associated with
traditional LSTM. Bidirectional LSTMs train two instead of one LSTMs on the input sequence.
The first on the input sequence as-is and the second on a reversed copy of the input sequence.
This can provide additional context to the network and result in faster and even fuller learning
of the concepts. The same training data used for the simple classifiers has been used to train
the LSTM models. A Bidirectional LSTM layer with 64 unit follows an input layer of 32 units.
The output is then connected to two dense layers activated by two types of functions: relu
and sigmoid (for binary prediction) with 64 and 1 unit respectively. In this pipeline we used
binary cross-entropy as the loss function and the Adam optimizer [
          <xref ref-type="bibr" rid="ref12">12</xref>
          ] to optimize the model
parameters. We identified the right stopping epoch by analyzing the validation accuracy and
thus finalizing the model parameters.
        </p>
      </sec>
      <sec id="sec-4-2">
        <title>4.2. Ensemble Methods</title>
        <p>
          Ensemble learning is a process where multiple diverse models are integrated in a way to
obtain better predictive performance than what could be obtained by each constituent model
independently. We created an Ensemble classifier of Random Forest, Logistic Regression and
SVM with the soft voting method [
          <xref ref-type="bibr" rid="ref13">13</xref>
          ]. The models used for Ensemble include a Random Forest
classifier with 2000 estimators, a Logistic Regression model and a Support Vector Machine using
a radial bias function. We used a Local Agnostic Model Interpretation approach to understand
the performance of the models before building the Ensemble.
        </p>
      </sec>
      <sec id="sec-4-3">
        <title>4.3. Lime Guided Ensemble Approach</title>
        <p>
          To have a better understanding of the models, we decided to used model explanation strategies.
LIME is a local agnostic model interpreter [
          <xref ref-type="bibr" rid="ref14">14</xref>
          ]. The advantage of using LIME is that it provides
uniform explanations across diferent models since it is model agnostic. It has been recently
been proposed by Sangani et.al.,2021 [
          <xref ref-type="bibr" rid="ref15">15</xref>
          ] to be used to compare the high performing models in
the Kaggle platform. LIME supports explanations on both regression and classification models.
We used LIME to compare the predictions of our models. The explanations are provided for each
model by means of highlighted text and a relevance bar chart [Fig.9]. The words highlighted
in orange denote a hate content, whereas those highlighted in blue support neutral decision.
They also provide a score for the overall final decision of the interpreter summarizing over the
highlighted words. We used LIME to analyse the shortcomings of each model and fine-tuned the
weights accordingly for the Ensemble technique. The best performance by the Ensemble models
was achieved by assigning a weight of 1,2 and 1 to the Logistic Regression, Random Forest, and
        </p>
        <p>
          SVM respectively. We chose the soft voting method over other methods as it predicts the class
label based on the argmax of the sums of the predicted probabilities, which is recommended for
an Ensemble of well-calibrated classifiers [
          <xref ref-type="bibr" rid="ref13">13</xref>
          ]. The particular LIME implementation we used
was time-consuming, hence we could only make a qualitative decision based on the manual
analysis of the limited number of explanations obtained for each model. We also had issues
trying to implement LIME in other models such as LSTM as a lot of processing was required
before and after training and prediction. We couldn’t fit LSTM into the LIME pipeline to give
explanations for predictions.
        </p>
        <p>The LIME explanations are provided in [Fig.9] and [Fig.10] for predictions made on a hateful
content and a neutral content by Random Forest, Logistic Regression, SVM, and Ensemble model
respectively. We used LIME for analysing 6 manually sampled instances from the dataset. From
[Fig.9] we can infer that SVM has done better than Logistic Regression and Random Forest as it
has assigned a higher weight to the word covidvaccine and other models have either made a
mistake or have assigned lesser weights.</p>
        <p>In [Fig.10] Random Forest has done best since it has the highest prediction score for hate
speech along with SVM. But SVM misses relevant words. Random forest has correctly classified
mattancock as a word of Hate Speech, unlike SVM which has mistaken it for Non-Hate Speech.
The Ensemble model’s prediction has also been explained and it is clearly visible that it has
used a combined result of all three models for its prediction making it unbiased and being able
to perform better.</p>
      </sec>
    </sec>
    <sec id="sec-5">
      <title>5. Fine Grained Classification for Subtask 1B</title>
      <p>
        For Subtask 1B which requires a multi-label classifier, we turned to DistilBERT [
        <xref ref-type="bibr" rid="ref16">16</xref>
        ]. Google
provides pre-trained partial BERT [
        <xref ref-type="bibr" rid="ref17">17</xref>
        ] language models which may be fine tuned based on our
application. BERT is designed to pre-train deep bidirectional representations from the unlabeled
text by jointly conditioning on both left and right context words. BERT uses the advantages of
transfer learning, a method where a model developed for a task is reused as the starting point for
a model on a second task. We have built DistilBERT, a model trained in a self-supervised fashion
using the BERT base model as a teacher. It is smaller and faster than BERT. We have trained
DistilBERT on the hate speech corpus [18]. The main reason for choosing this model, unlike
other sequence classifiers like RNN is that, the DistilBERT model works on the entire sequence
at once instead of reading the tokens sequentially. This process can be further accelerated using
GPU support provided by Google Colab. We could adapt the pre-trained DistilBERT model by
training it further on our relatively smaller dataset, further fine-tuning the parameters for better
accuracy without much computational overhead. The tweets in the dataset were of diferent
lengths. We used padding to normalize all the tweets to have the maximum sequence length.
The DistilBERT model we chose was pre-trained on unlabelled Wikipedia corpus. It was then
ifne-tuned for our corpus by adding the output layer.
      </p>
      <p>The DistilBERT [18] model we chose facilitated in developing a multi label regression classifier.
The output vector from the model is a 4-dimensional numeric vector. We used one-hot encoding
on the class labels of the existing HASOC dataset to obtain a 4-dimensional boolean output
vector for each tweet. The first value of the vector indicates hate class, the second profane,
the third ofensive and the fourth represents neutral. For eg., a tweet that is profane will be
encoded [0 1 0 0]. While classifying a tweet using DistilBERT, on obtaining the 4 dimensional
output vector, the tweet is assigned the class corresponding to the vector position which has
the highest numerical value.</p>
    </sec>
    <sec id="sec-6">
      <title>6. Results</title>
      <sec id="sec-6-1">
        <title>6.1. Metrics For Comparison</title>
        <p>The models were compared using precision, recall, F-Measure and accuracy.
• Precision: Precision is also known as the positive predicted value. It is the proportion of
predictive positives which are actually positive (true positives).
• Recall: It is the proportion of actual positives which are predicted positive.
• F-Measure: It is the harmonic mean of precision and recall. The standard F-measure (F1)
gives equal importance to precision and recall.
• Accuracy: It is the number of correctly classified instances (true positives and true
negatives).</p>
      </sec>
      <sec id="sec-6-2">
        <title>6.2. Comparing the Models for Subtask 1A</title>
        <p>For Subtask 1A the combined training dataset from HASOC and Kaggle were used for training
and the test dataset was randomly sampled from the HASOC training dataset. The split was
90:10 for training and testing. We have experimented with the HASOC dataset as well as the
combined dataset. In both cases the test cases were sampled from the HASOC test dataset. The
augmented kaggle dataset did play a significant role to improve the accuracy of Ensemble and
Random Forest while it decreased the performance for the others such as Logistic Regression,
Bidirectional LSTM and SVM. We have tabulated the best results obtained for the diferent
models among the diferent training sets used.</p>
        <p>The performance of Random Forest and Ensemble models trained on the combined HASOC
and Kaggle datasets and the other models trained on the HASOC dataset have been provided in
Table 2. The data has been ordered based on accuracy. From the plots 11 and 12 we can infer
that the Ensemble model performs much better than the independent models as it combines the
advantages of all the other models and reduces the ill efects of each model.</p>
        <p>We have trained the LSTM model for 100 epochs, at which it gives the best performance.
LSTM model does not fare well compared to other models with a Macro F1 of just 0.7198. Yet it
provides valuable insights about the hate words through embedding vectors that we projected
using embedding projectors explained in section 3. With more data the model could have
performed better by learning improved hate word embeddings and understanding the context
better.</p>
        <p>Although from the given LIME examples the significance of the Logistic Regression model
in the Ensemble might not be visible, we could get the best Ensemble performance only when
Logistic Regression was included.</p>
      </sec>
      <sec id="sec-6-3">
        <title>6.3. Comparison between Fine tuned and Untuned DistilBERT Models for</title>
      </sec>
      <sec id="sec-6-4">
        <title>Subtask 1B</title>
        <p>For Subtask 1B we tested two versions of DistilBERT model on a 90:10 training and test data
split of the HASOC dataset. The untuned initial version has 4 hidden layers each with 128, 64,
32 and 4 units. We removed the hidden layer with 128 units while fine tuning the DistilBERT
model. To prevent underfitting we reduced dropout from 0.1 to 0.05. We trained the fine tuned
DistilBERT model for 6 epochs, unlike the untuned version which had only 5 epochs. The major
changes that led to a colossal increase in accuracy were basically with respect to simplifying the
hidden layer, reducing the drop out and increasing the training epochs. The results are found in
Table 3.</p>
      </sec>
    </sec>
    <sec id="sec-7">
      <title>7. Conclusion</title>
      <p>We classified the Hate Speech dataset provided by the HASOC Track 1 of FIRE 2021. Though
Subtask 1A is a simple binary classifier we could not achieve the expected accuracy and stood
25th out of the total 56 submissions [Fig.13]. The reason is that Subtask 1A had a limited data
and our decision to augment it with more data from Kaggle probably did not work. Meanwhile,
we observed that an Ensemble method improved our accuracy over other approaches used.
Work is under progress in this line to quantify the interpretations provided by LIME. The
multigrain classification problem was the toughest with the benchmark performance as low as
0.5 (Precision and F1 score). With respect to the fine-grained classifier developed for Subtask
1B, DistilBERT gave superior performance compared to other approaches and scored the 8th
rank among the total 37 submissions [Fig.14]. It is interesting to note that both Subtask 1A and
Subtask 1B required entirely diferent approaches though they were all Hate Speech classifiers.
and domain knowledge, IEEE Access 7 (2019) 176600–176612. doi:1 0 . 1 1 0 9 / A C C E S S . 2 0 1 9 .
2 9 5 3 9 9 0 .
[18] R. Mutanga, N. Naicker, O. O. Olugbara, Hate speech detection in twitter using transformer
methods, International Journal of Advanced Computer Science and Applications 11 (2020).</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>J.</given-names>
            <surname>Nockleyby</surname>
          </string-name>
          ,
          <article-title>Hate speech in encyclopedia of the american constitution</article-title>
          ,
          <source>Electronic Journal of Academic and Special librarianship</source>
          (
          <year>2000</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>T.</given-names>
            <surname>Guardian</surname>
          </string-name>
          ,
          <article-title>Zuckerberg on refugee crisis: 'hate speech has no place on facebook</article-title>
          ',
          <year>2016</year>
          . URL: https://www.theguardian.com/technology/2016/feb/26/ mark-zuckerberg
          <article-title>-hate-speech-germany-facebook-refugee-crisis.</article-title>
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>Z.</given-names>
            <surname>Zhang</surname>
          </string-name>
          , L. Luo,
          <article-title>Hate speech detection: A solved problem? the challenging case of long tail on twitter</article-title>
          ,
          <source>Semantic Web</source>
          <volume>10</volume>
          (
          <year>2019</year>
          )
          <fpage>925</fpage>
          -
          <lpage>945</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>T.</given-names>
            <surname>Mandl</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Modha</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Majumder</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Patel</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Dave</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Mandalia</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Patel</surname>
          </string-name>
          ,
          <source>Overview of the HASOC track at FIRE</source>
          <year>2019</year>
          :
          <article-title>Hate speech and ofensive content identification in indoeuropean languages</article-title>
          ,
          <source>Proceedings of the 11th Forum for Information Retrieval Evaluation</source>
          (
          <year>2019</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>S.</given-names>
            <surname>Modha</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Mandl</surname>
          </string-name>
          ,
          <string-name>
            <given-names>G. K.</given-names>
            <surname>Shahi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            <surname>Madhu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Satapara</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Ranasinghe</surname>
          </string-name>
          ,
          <string-name>
            <surname>M.</surname>
          </string-name>
          <article-title>Zampieri, Overview of the HASOC Subtrack at FIRE 2021: Hate Speech and Ofensive Content Identification in English and Indo-Aryan Languages and Conversational Hate Speech</article-title>
          , in: FIRE 2021:
          <article-title>Forum for Information Retrieval Evaluation, Virtual Event</article-title>
          ,
          <fpage>13th</fpage>
          -17th
          <source>December</source>
          <year>2021</year>
          , ACM,
          <year>2021</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <given-names>T.</given-names>
            <surname>Mandl</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Modha</surname>
          </string-name>
          ,
          <string-name>
            <given-names>G. K.</given-names>
            <surname>Shahi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            <surname>Madhu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Satapara</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Majumder</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Schäfer</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Ranasinghe</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Zampieri</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Nandini</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A. K.</given-names>
            <surname>Jaiswal</surname>
          </string-name>
          ,
          <article-title>Overview of the HASOC subtrack at FIRE 2021: Hate Speech and Ofensive Content Identification in English and Indo-Aryan Languages</article-title>
          , in: Working Notes of FIRE 2021 -
          <article-title>Forum for Information Retrieval Evaluation</article-title>
          ,
          <string-name>
            <surname>CEUR</surname>
          </string-name>
          ,
          <year>2021</year>
          . URL: http://ceur-ws.org/.
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <given-names>J. E.</given-names>
            <surname>Ramos</surname>
          </string-name>
          ,
          <article-title>Using tf-idf to determine word relevance in document queries</article-title>
          ,
          <year>2003</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <given-names>O.</given-names>
            <surname>Oriola</surname>
          </string-name>
          ,
          <string-name>
            <surname>E. Kotzé,</surname>
          </string-name>
          <article-title>Evaluating machine learning techniques for detecting ofensive and hate speech in south african tweets</article-title>
          ,
          <source>IEEE Access 8</source>
          (
          <year>2020</year>
          )
          <fpage>21496</fpage>
          -
          <lpage>21509</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <given-names>F.</given-names>
            <surname>Pedregosa</surname>
          </string-name>
          ,
          <string-name>
            <given-names>G.</given-names>
            <surname>Varoquaux</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Gramfort</surname>
          </string-name>
          ,
          <string-name>
            <given-names>V.</given-names>
            <surname>Michel</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Thirion</surname>
          </string-name>
          ,
          <string-name>
            <given-names>O.</given-names>
            <surname>Grisel</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Blondel</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Prettenhofer</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Weiss</surname>
          </string-name>
          ,
          <string-name>
            <given-names>V.</given-names>
            <surname>Dubourg</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Vanderplas</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Passos</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Cournapeau</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Brucher</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Perrot</surname>
          </string-name>
          , E. Duchesnay,
          <article-title>Scikit-learn: Machine learning in Python</article-title>
          ,
          <source>Journal of Machine Learning Research</source>
          <volume>12</volume>
          (
          <year>2011</year>
          )
          <fpage>2825</fpage>
          -
          <lpage>2830</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <given-names>D.</given-names>
            <surname>Robinson</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Z.</given-names>
            <surname>Zhang</surname>
          </string-name>
          , J. Tepper,
          <article-title>Hate speech detection on twitter: Feature engineering vs feature selection</article-title>
          ,
          <source>in: European Semantic Web Conference</source>
          , Springer,
          <year>2018</year>
          , pp.
          <fpage>46</fpage>
          -
          <lpage>49</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [11]
          <string-name>
            <given-names>M.</given-names>
            <surname>Sundermeyer</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Schlüter</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            <surname>Ney</surname>
          </string-name>
          ,
          <article-title>Lstm neural networks for language modeling</article-title>
          ,
          <source>in: Thirteenth annual conference of the international speech communication association</source>
          ,
          <year>2012</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          [12]
          <string-name>
            <given-names>D.</given-names>
            <surname>Kingma</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Ba</surname>
          </string-name>
          ,
          <article-title>Adam: A method for stochastic optimization</article-title>
          ,
          <source>International Conference on Learning Representations</source>
          (
          <year>2014</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          [13]
          <string-name>
            <given-names>F.</given-names>
            <surname>Pedregosa</surname>
          </string-name>
          ,
          <string-name>
            <given-names>G.</given-names>
            <surname>Varoquaux</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Gramfort</surname>
          </string-name>
          ,
          <string-name>
            <given-names>V.</given-names>
            <surname>Michel</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Thirion</surname>
          </string-name>
          ,
          <string-name>
            <given-names>O.</given-names>
            <surname>Grisel</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Blondel</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Prettenhofer</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Weiss</surname>
          </string-name>
          ,
          <string-name>
            <given-names>V.</given-names>
            <surname>Dubourg</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Vanderplas</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Passos</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Cournapeau</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Brucher</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Perrot</surname>
          </string-name>
          , E. Duchesnay,
          <article-title>Scikit-learn: Machine learning in Python</article-title>
          ,
          <source>Journal of Machine Learning Research</source>
          <volume>12</volume>
          (
          <year>2011</year>
          )
          <fpage>2825</fpage>
          -
          <lpage>2830</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          [14]
          <string-name>
            <given-names>M. T.</given-names>
            <surname>Ribeiro</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Singh</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Guestrin</surname>
          </string-name>
          , ”
          <article-title>why should i trust you?”: Explaining the predictions of any classifier</article-title>
          ,
          <year>2016</year>
          .
          <article-title>a r X i v : 1 6 0 2 . 0 4 9 3 8</article-title>
          .
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          [15]
          <string-name>
            <surname>R. B. Sangani</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          <string-name>
            <surname>Shukla</surname>
            ,
            <given-names>R. B.</given-names>
          </string-name>
          <string-name>
            <surname>Selvamani</surname>
          </string-name>
          ,
          <article-title>Comparing deep sentiment models using quantified local explanations, in: Accepted for publication in Proceedings of IEEE-Smart Technologies</article-title>
          , Communication Robotics 2021 Conference, IEEE,
          <year>2021</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          [16]
          <string-name>
            <given-names>V.</given-names>
            <surname>Sanh</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Debut</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Chaumond</surname>
          </string-name>
          , T. Wolf,
          <article-title>Distilbert, a distilled version of bert: smaller, faster, cheaper and lighter</article-title>
          , ArXiv abs/
          <year>1910</year>
          .01108 (
          <year>2019</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          [17]
          <string-name>
            <given-names>S.</given-names>
            <surname>Yu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Su</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Luo</surname>
          </string-name>
          ,
          <article-title>Improving bert-based text classification with auxiliary sentence</article-title>
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>