<!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>Classification of Hate, Ofensive and Profane content from Tweets using an Ensemble of Deep Contextualized and Domain Specific Representations</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Basavraj Chinagundi</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Muskaan Singh</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Tirthankar Ghosal</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Prashant Singh Rana</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Guneet Singh Kohli</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Institute of Formal and Applied Linguistics, Faculty of Mathematics and Physics, Charles University</institution>
          ,
          <country country="CZ">Czech Republic</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Thapar Institute of Engineering and Technology</institution>
          ,
          <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>The explosive growth of social media has also resulted in unfortunate emergence of hate, ofensive, and profane content on the web. A certain conversational thread can contain hate, ofensive, and profane content, which is not apparent from a standalone or single tweet or replies but can be identified if given the context of the parent content. Such social media content is spread in many diferent languages, including code-mixed languages like hinglish (English code-mixed with Hindi). So it becomes a huge responsibility for the social media sites to identify such hate content before it gets disseminated to the general population, which may trigger havoc. The hate speech and ofensive content identification track (HASOC)[1] in FIRE 2021 English Subtask A track provides a forum and a data challenge for multilingual research on the identification of such problematic content. In this paper, we describe our submission for the above track. Our proposed approach uses a transformer-based embedding with HateBERT and achieves the Macro F1 score of 79% on the test data, which is 3.96% behind the best-performing system. We make our system run available at https://github.com/basavraj-chinagundi/HASOC_2021</p>
      </abstract>
      <kwd-group>
        <kwd>eol&gt;hate Speech</kwd>
        <kwd>Text Classification</kwd>
        <kwd>Profane Content</kwd>
        <kwd>HateBERT</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. Introduction</title>
      <p>Social media sites like Twitter and Facebook, being user-friendly and a free source , provide
opportunities for people to air their voices. People, irrespective of age group, use these sites
to share every moment of their lives, making these sites flooded with data. Apart from these
commendable features of social media, they also have downsides as well. Due to the lack of
restrictions set by these sites for their users to express their views as they like, anyone can
make adverse and unrealistic comments in abusive language against anybody with an ulterior
motive to tarnish one’s image and status in society. A conversational thread can also contain
hate 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. Furthermore, the contents on such
social media are spread in so many diferent languages, including code-mixed languages such
as hinglish. So it becomes a huge responsibility for these sites to identify such hate content
before it disseminates to the masses. The best performing model in our study is based on
Transformer contextual embedding and HateBERT architecture. When compared to traditional
and ensembled machine learning models, the presented solution enhances accuracy by 6-9% on
average. The HateBERT based model achieves a competitive f1 score of 0.7909, demonstrating
potential for further improvement in performance</p>
    </sec>
    <sec id="sec-2">
      <title>2. Related Work</title>
      <p>
        Most of the previous works in the field use surface features, word embedding features, lexical
resources, meta-information, linguistic study, cross-domain information, dealing with biases
and multi-task learning. The problem of classifying any sentence as hate is challenging. There
might be cases when a sentence containing slang might be classified as hate, because of the
words having diferent meanings in a diferent context. It afects the right to freedom of speech
with the kind of words being used on social media. [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ] used SVM with syntactic and semantic
information of word-n-grams. [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ] presents logistic regression model performance with feeding
TF-IDF values and unigram, bigrams, trigrams featured weights achieve 90% precision with
61% correctly predicting hate class. [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ] classified ontological classes of harmful speech based
on diferent parameters such as degree of content, intent and its efect on social media. [ 5]
annotated a dataset of 16K tweets using race theory releases publicly. They also did performance
analysis on geographic, word length distribution does not have a significant impact while gender
information combined with char-n-grams shows some significant improvement. [ 6] uses four
features (such as linguistic, syntactic, distributional, n-gram) to diferentiate between abusive
and clean features in news and financial data. [ 7] identified racist and radicalized intent on
Tumblr microblogging website using semantic, sentiment and linguistic features with cascaded
ensemble learning classifier. [ 8] provided an annotated corpora of 80K tweets categorized into
8 labels, for studying diferent types of abusive behaviour. [ 9] uses features such as sentiment,
semantic, unigrams and pattern-based to classify 2010 sentences. [10] released a data set of 2435
tweets on refugees and Muslims and a new novel approach using CNN-GRU architecture. Their
approach shows promising results for 6 out of 7 data sets. outperforming other state-of-art by 13
F1 scores. [11] applied bag-of-words to learn a classifier for the labels racist and non-racist with
76% accuracy. [12] combines LSTM model and neural-based GBDT word embedding on dataset
[5]. [13] combined char-CNN and word-CNN by formulating a hybrid CNN which performed
well than classic methods like logistic regression and SVM on a data set of 16k tweets by [5]. It
ifrstly detected the abusive language and then classified it into specific types of abuse. Further
[14] also use CNN with random vectors, word vectors based on semantic information, word
vectors combined with character 4-grams. It also presents a comparative performance analysis.
      </p>
    </sec>
    <sec id="sec-3">
      <title>3. Task Description</title>
      <p>A conversational thread contains hate, ofensive, and profane content, which is not apparent
from a standalone or single tweet or comment or the reply to a comment, but can be identified if
given the context of the parent content is known. In reference to fig:example the screenshot from
Twitter describes the problem at hand efectively. The parent/source tweet, which was posted
at 2:30 am on May 11th, expresses Hate and profanity towards Muslim countries regarding the
controversy happening during the recent Israel-Palestine conflict. The 2 comments on the tweet
have written ”Amine”, which means trustworthy or honest in Arabic. If the 2 comments were
to be analyzed for hate or ofensive speech without the context of the parent tweet, they would
not be classified as hate or ofensive content. But if we take the context of the conversation,
then we can say that the comments support the hate expressed in the parent tweet. So those
comments are labelled as hate/ofensive/profane. The English sub-task A [ 16] focused on the
binary classification of such conversational tweets with tree-structured data into:
• (NOT) Non hate-Ofensive This tweet, comment, or reply does not contain any hate
speech, profane, ofensive content.
• (HOF) hate and Ofensive This tweet, comment, or reply contains hate, ofensive, and
profane content in itself or supports hate expressed in the parent tweet.</p>
      <p>Another such example with code mixed text. The Source Tweet: “Modi Ji COVID situation ko
solve karne ke liye ideas maang rahe the. Mera idea hai resignation dedo please. ”
• Translation : Modi ji (PM of India) was asking for ideas to solve the covid situation of</p>
      <p>India. My idea to him is to resign.
• The Comment: Doctors aur Scientists se manga hai. Chutiyo se nahi. Baith niche. [HOF]
• Translation: They have asked Doctors and Scientists. Not fuckers. Sit down. [HOF]
• The reply: You totally nailed it, can’t stop laughing. [HOF]
The reply has a positive sentiment. But it is positive in favour of the hate expressed towards
the author of the source tweet in the comment. Hence, it is supporting the hate expressed in
the comment. Hence, it is also hate speech. This is the type of problem we’re aiming to solve
via this shared task.</p>
    </sec>
    <sec id="sec-4">
      <title>4. Dataset Description</title>
      <p>We experiment with a collection of diverse datasets comprising of foul and ofensive tweets,
comments acquired from various sources. The dataset[17] used for training consists a total
of 76601 texts which are either hate speech and ofensive (40823) or normal (35778). We have
collected these samples from namely 6 sources like:
1. HSOL[18]: HSOL is a dataset for hate speech identification that includes a hate speech
lexicon including words and phrases recognised as hate speech by internet users and
collected by hatebase.org. Using the Twitter API, they searched for tweets containing
phrases from the lexicon, yielding a sample of tweets from 33,458 Twitter users. They
retrieved the timeline for each user, yielding a collection of 85.4 million tweets. From this
dataset, they selected a random sample of 25k tweets containing lexical words and had
them manually coded by CrowdFlower (CF) employees. Workers were asked to categorise
each tweet into one of three categories: hate speech, ofensive but not hate speech, or
neither ofensive nor hate speech.
2. OLID[19]:OLID is a hierarchical dataset to identify the type and the target of ofensive
texts in social media. The dataset was compiled via Twitter and is freely accessible to the
public. There are 14,100 tweets in all, with 13,240 in the training set and 860 in the test
set. There are three degrees of labelling for each tweet: (A) Ofensive/Not-Ofensive, (B)
Targeted-Insult/Untargeted, and (C) Individual/Group/Other. If a tweet is ofensive, it
might have a target or no target. If it is ofensive to a specified target, the target might be
an individual, a group, or any other thing. This dataset is utilised in the OfensEval-2019
competition at SemEval-2019.
3. hatespeech [20]: Dataset of hate speech annotated at the sentence level from Internet
forum postings in English. Stormfront, a prominent online community of white
nationalists, is where the source forum can be found. A total of 10,568 sentences were taken from
Storm front and labelled as hate speech or not.
4. TRAC[21]: The data set consists of 15,000 aggression-annotated Facebook Posts and
Comments that include labels for three-way categorization of text data into ‘Overtly
Aggressive, ’ ‘Covertly Aggressive, ’ and ‘Non-aggressive. ’
5. ETHOS[22]: ETHOS is a data set for detecting hate specks. It is made up of YouTube
and Reddit comments that have been verified using a crowd sourcing tool. It is divided
into two subsets: one for binary classification and one for multi-label classification. The
one used for our experiment is the binary subset. The former has 998 comments, whereas
the latter has 433 comments with fine-grained hate-speech annotations.
6. HASOC[23]: The dataset focuses on hate speech and ofensive language detection in
English. The data set is classified into two classes, namely: hate and Ofensive (HOF)
consisting 5051 tweets and Non- hate and ofensive (NOT) consisting 5798 tweets
respectively.</p>
    </sec>
    <sec id="sec-5">
      <title>5. Methodology</title>
      <sec id="sec-5-1">
        <title>5.1. Pre-processing</title>
        <p>In the methodology we describe the pre-processing and explain diferent baselines along with
submitted experiments for classifying hate content as shown in Figure 2.</p>
        <p>We first went with lower casing each tweet/comment in the data set. Secondly, hashtags are
very critical while retrieving sentiment of a text, therefore we preprocess the hashtags using
a tailored technique. We start by creating a data frame of all hashtags in a column and their
counts. After that we remove numbers and segment multiple words using hash fix function
which basically splits the word into segments using the word segment library. Finally we create
a dictionary of the hashtags and their clean strings. For example if we have hashtags consisting
of multiple words such as #fuckdick it will split the above token into fuck and dick respectively,
enhancing the ability to retrieve significant words which are critical for classification of the
text as a negative sentiment. We further remove other irrelevant parts of the texts such as
usernames, some special characters, retweet tags etc.</p>
      </sec>
      <sec id="sec-5-2">
        <title>5.2. Model Description</title>
        <p>The next step is extracting features from the text for which we use TF-IDF vectorizer to transform
text into a meaningful representation of numbers which is then used to fit machine algorithm
such as NB, LR, KNN, SVM, DT, RF, Bagging, AdaBoost and voting in Table 1 for classifying our
text as hate speech or not. We also experiment with another word embedding technique GloVe
(840B tokens, 2.2M vocab, cased, 300 dimension vectors) which is an unsupervised learning
algorithm for obtaining vector representations for words.</p>
        <p>We test out multiple machine learning algorithms and also use ensemble learning in order
to produce one optimal predictive model. Now to produce even better results, we try out
transformer based pre-trained models:
1. Ernie 2.0 [24]
2. Twitter Roberta Base Ofensive [ 25]
3. HateBERT [20]
The deep learning based models have their own embeddings which were used to extract features
from the text. In the final step we fine tune these three models on our combined dataset and
boost the results for the classification of text as hateful and ofensive.</p>
      </sec>
    </sec>
    <sec id="sec-6">
      <title>6. Experiment and Results</title>
      <p>After extracting features with TF-IDF We first use a logistic regression with L2 regularization
as it disperses the error terms in all the weights and leads to more accurate customized final
models. We then test a variety of models that have been used in prior work: logistic
regression, naive Bayes, decision trees, random forests, k-nearest neighbors (KNN), and linear SVMs.
We then try bagging method using decision tree classifier with parameters set as
max_samples=0.5, max_features=1.0, n_estimators=10. We also check AdaBoostClassifier using decision
trees with parameters min_samples_split=10, max_depth=4, n_estimators=10, learning_rate=0.6.
We tested each model using 5-fold cross validation, holding out 10 percent of the sample for
evaluation to help prevent over-fitting. After using a grid-search to iterate over the models and
parameters we find that the Logistic regression, naive bayes, random forest and Linear SVM
tend to perform significantly better than other models. So by ensembling these we make another
model using voting classifier. When comparing all these models we see that logistic regression
with tfidf vector representation performs the best having 0.77 accuracy, macro avg f1 score of 0.75
and weighted avg f1 score of 0.76 respectively. We then experiment using GloVe represtation and
ensembling ML algorithms namely naive bayes, logistic regression and multilayer perceptron
and find out that it doesn’t necessarily boost the performance of our model achieving accuracy
of 0.72, macro avg f1 score of 0.71 and weighted avg f1 score of 0.72. Thus we move onto our final
set of experimentations. We use transformer based pretrained models as a transformer is to able
to parallely process the words in the sentences and get contexualized embeddings. This parallel
processing is not possible in LSTMs or RNNs or GRUs as they take words of the input sentence
as input one by one. We ran all three pretrained models for 5 epochs by fine tuning it with
hyperparameters having batch size 16 and Adam optimizer with learning rate 1e-5 , eps=1e-8.
Ernie 2.0 improved the performance in comparison to the previous experiments we ran using
word embeddings and machine learning algorithms, achieving 0.80 accuracy, macro avg f1 score
of 0.78 and weighted avg f1 score of 0.80 respectively. TwitterRobertaBaseOfensive which is a
pretrained model trained on 58M tweets and finetuned for ofensive language identification with
the TweetEval benchmark further increased the performance attaining 0.81 accuracy, macro
avg f1 score of 0.79 and weighted avg f1 score of 0.81. Finally we test another pretrained model
HateBERT which was was trained on RAL-E, a large-scale dataset of Reddit comments in English
from communities banned for being ofensive, abusive, or hateful that we have collected and
made available to the public. It performed the best optimally amongst all the pretrained models
achieving same accuracy and f1 scores as TwitterRobertaBaseOfensive but having slightly
better performance in recall metrics for classifying text as HOF and NOT hate respectively,
overall leading to a much more balanced model. The Google colab’s Tesla P100-pcie-16GB with
8 core CPU and 32GB RAM was used for the experimental setup.</p>
    </sec>
    <sec id="sec-7">
      <title>7. Conclusion</title>
      <p>In this paper, we present our submission to classify hate content from the tweets and comments.
The recent trend of hateful speech has increased and has posed a lot of challenge in discriminating
hate speech against freedom of speech. One post can mean diferently in diferent context as
there is no universally accepted definition of hate speech.</p>
      <p>There are diferent benchmark depending upon demography, social influence and cultural
factors. We propose, a deep learning model based on Transformer contextual embedding and
HateBERT architecture. We pre-processed the tweet from HASOC 2021 data set, extracted
features embedding and trained our system to classify into hate speech or not with 79% macro
F1 score. The work compiled showcases the scope of HateBERT in being employed for further
experimentation and being optimised for better performances by focusing on newer embedding
combinations and ensemble approaches.
twitter data, arXiv preprint arXiv:1806.04197 (2018).
[5] Z. Waseem, D. Hovy, Hateful symbols or hateful people? predictive features for hate
speech detection on twitter, in: Proceedings of the NAACL student research workshop,
2016, pp. 88–93.
[6] C. Nobata, J. Tetreault, A. Thomas, Y. Mehdad, Y. Chang, Abusive language detection in
online user content, in: Proceedings of the 25th international conference on world wide
web, 2016, pp. 145–153.
[7] S. Agarwal, A. Sureka, Characterizing linguistic attributes for automatic classification of
intent based racist/radicalized posts on tumblr micro-blogging website, arXiv preprint
arXiv:1701.04931 (2017).
[8] A. M. Founta, C. Djouvas, D. Chatzakou, I. Leontiadis, J. Blackburn, G. Stringhini, A. Vakali,
M. Sirivianos, N. Kourtellis, Large scale crowdsourcing and characterization of twitter
abusive behavior, in: Twelhft International AAAI Conference on Web and Social Media,
2018.
[9] H. Watanabe, M. Bouazizi, T. Ohtsuki, Hate speech on twitter: A pragmatic approach to
collect hateful and ofensive expressions and perform hate speech detection, IEEE access 6
(2018) 13825–13835.
[10] Z. Zhang, D. Robinson, J. Tepper, Detecting hate speech on twitter using a convolution-gru
based deep neural network, in: European semantic web conference, Springer, 2018, pp.
745–760.
[11] I. Kwok, Y. Wang, Locate the hate: Detecting tweets against blacks, in: Twenty-seventh</p>
      <p>AAAI conference on artificial intelligence, 2013.
[12] P. Badjatiya, S. Gupta, M. Gupta, V. Varma, Deep learning for hate speech detection
in tweets, in: Proceedings of the 26th international conference on World Wide Web
companion, 2017, pp. 759–760.
[13] J. H. Park, P. Fung, One-step and two-step classification for abusive language detection on
twitter, arXiv preprint arXiv:1706.01206 (2017).
[14] B. Gambäck, U. K. Sikdar, Using convolutional neural networks to classify hate-speech, in:</p>
      <p>Proceedings of the first workshop on abusive language online, 2017, pp. 85–90.
[15] Hasoc, https://hasocfire.github.io/hasoc/2021/index.html, 2021. Accessed: 2021-11-27.
[16] T. Mandl, S. Modha, G. Shahi, H. Madhu, S. Satapara, P. Majumder, J. Schäfer, T. Ranasinghe,
M. Zampieri, D. Nandini, et al., Overview of the hasoc subtrack at fire 2021: Hate speech
and ofensive content identification in english and indo-aryan languages, Working Notes
of FIRE (2021).
[17] B. Dave, S. Bhat, P. Majumder, Irnlp_daiict@ lt-edi-eacl2021: Hope speech detection in
code mixed text using tf-idf char n-grams and muril, in: Proceedings of the First Workshop
on Language Technology for Equality, Diversity and Inclusion, 2021, pp. 114–117.
[18] T. Davidson, D. Warmsley, M. Macy, I. Weber, Automated hate speech detection and the
problem of ofensive language, in: Proceedings of the 11th International AAAI Conference
on Web and Social Media, ICWSM ’17, 2017, pp. 512–515.
[19] S. Rosenthal, P. Atanasova, G. Karadzhov, M. Zampieri, P. Nakov, A large-scale
semisupervised dataset for ofensive language identification, arXiv preprint arXiv:2004.14454
(2020).
[20] T. Caselli, V. Basile, J. Mitrović, M. Granitzer, Hatebert: Retraining bert for abusive
language detection in english, arXiv preprint arXiv:2010.12472 (2020).
[21] Trac, https://sites.google.com/view/trac1/home, 2021. Accessed: 2021-11-27.
[22] I. Mollas, Z. Chrysopoulou, S. Karlos, G. Tsoumakas, Ethos: an online hate speech detection
dataset, arXiv preprint arXiv:2006.08328 (2020).
[23] P. Alonso, R. Saini, G. Kovács, Hate speech detection using transformer ensembles on the
hasoc dataset, in: International Conference on Speech and Computer, Springer, 2020, pp.
13–21.
[24] Y. Sun, S. Wang, Y. Li, S. Feng, H. Tian, H. Wu, H. Wang, Ernie 2.0: A continual
pretraining framework for language understanding, in: Proceedings of the AAAI Conference
on Artificial Intelligence, volume 34, 2020, pp. 8968–8975.
[25] F. Barbieri, J. Camacho-Collados, L. Neves, L. Espinosa-Anke, Tweeteval: Unified
benchmark and comparative evaluation for tweet classification, arXiv preprint arXiv:2010.12421
(2020).
[26] S. Satapara, S. Modha, T. Mandl, H. Madhu, P. Majumder, Overview of the hasoc subtrack
at fire 2021: Conversational hate speech detection in code-mixed language, Working Notes
of FIRE (2021).</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>S.</given-names>
            <surname>Modha</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Mandl</surname>
          </string-name>
          , G. Shahi,
          <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>
          ,
          <year>2021</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>H.</given-names>
            <surname>Chen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>McKeever</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S. J.</given-names>
            <surname>Delany</surname>
          </string-name>
          ,
          <article-title>Abusive text detection using neural networks</article-title>
          .,
          <source>in: Artificial Intelligence and Cognitive Science (AICS)</source>
          ,
          <year>2017</year>
          , pp.
          <fpage>258</fpage>
          -
          <lpage>260</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>T.</given-names>
            <surname>Davidson</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Warmsley</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Macy</surname>
          </string-name>
          ,
          <string-name>
            <surname>I. Weber</surname>
          </string-name>
          ,
          <article-title>Automated hate speech detection and the problem of ofensive language</article-title>
          ,
          <source>in: Proceedings of the International AAAI Conference on Web and Social Media</source>
          , volume
          <volume>11</volume>
          ,
          <year>2017</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>S.</given-names>
            <surname>Sharma</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Agrawal</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Shrivastava</surname>
          </string-name>
          ,
          <article-title>Degree based classification of harmful speech using</article-title>
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>