<!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>Crowdsourcing of Parallel Corpora: the Case of Style Transfer for Detoxification</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Daryna Dementieva</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Sergey Ustyantsev</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>David Dale</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Olga Kozlova</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Nikita Semenov</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Alexander Panchenko</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Varvara Logacheva</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Mobile TeleSystems (MTS)</institution>
          ,
          <addr-line>Moscow</addr-line>
          ,
          <country country="RU">Russia</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Skolkovo Institute of Science and Technology</institution>
          ,
          <addr-line>Moscow</addr-line>
          ,
          <country country="RU">Russia</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>One of the ways to fighting toxicity online is to automatically rewrite toxic messages. This is a sequenceto-sequence task, and the easiest way of solving it is to train an encoder-decoder model on a set of parallel sentences (pairs of sentences with the same meaning, where one is ofensive and the other is not). However, such data does not exist, making researchers resort to non-parallel corpora. We close this gap by suggesting a crowdsourcing scenario for creating a parallel dataset of detoxifying paraphrases. In our first experiments, we collect paraphrases for 1,200 toxic sentences. We describe and analyse the crowdsourcing setup and the resulting corpus.</p>
      </abstract>
      <kwd-group>
        <kwd>eol&gt;toxicity</kwd>
        <kwd>dataset</kwd>
        <kwd>crowdsourcing</kwd>
        <kwd>parallel data</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. Introduction</title>
      <p>
        Toxicity is a major problem on the Internet. There are multiple strategies for fighting it.
Detection of toxicity, being a popular area of research in NLP [
        <xref ref-type="bibr" rid="ref1 ref2 ref3">1, 2, 3</xref>
        ], is a necessary first step
for any toxicity removal strategy. There exist multiple methods for toxicity detection [
        <xref ref-type="bibr" rid="ref4 ref5">4, 5</xref>
        ] and
datasets [
        <xref ref-type="bibr" rid="ref6 ref7 ref8">6, 7, 8</xref>
        ] which can be used as training data for toxicity detection models.
      </p>
      <p>Toxic messages can difer in terms of their content. For some of them, the ofence is the only
content, and their only goal is to insult the reader. On the other hand, other messages classified
as toxic can contain a non-toxic and useful content that is only expressed in a toxic way. If we
manage to rewrite such messages to eliminate the toxicity and save the content, we will be able
to keep a constructive and peaceful discussion and prevent it from decaying to a row of insults.</p>
      <p>
        The task of detoxification of text has already been tackled by several researchers [
        <xref ref-type="bibr" rid="ref10 ref11 ref9">9, 10, 11</xref>
        ].
This task is usually formulated as a style transfer task [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ] — a task of rewriting a text with
keeping the original content as much as possible and changing a particular attribute (author
profile, text sentiment, degree of complexity, etc.). This attribute is referred to as style. In the case
of detoxification, the task is to transfer text from toxic to neutral (non-toxic) style. It is similar
to the tasks of rewriting texts with a varying degree of formality [
        <xref ref-type="bibr" rid="ref13 ref14">13, 14</xref>
        ] or politeness [
        <xref ref-type="bibr" rid="ref15 ref16">15, 16</xref>
        ].
      </p>
      <p>
        As with many other sequence-to-sequence tasks (machine translation, text summarization,
paraphrasing), style transfer can be successfully solved using encoder-decoder models trained
on parallel data [
        <xref ref-type="bibr" rid="ref14 ref17">14, 17</xref>
        ]. This is the easiest training setup because it contains a correct answer
towards which a model can be optimised. However, for the majority of style transfer tasks,
the parallel data is unavailable [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ]. Therefore, style transfer models are usually trained on
non-parallel datasets. If parallel data was available, they could perform better with smaller
training corpora. The experiments show that training even on an extremely small parallel
dataset can yield a well-performing style transfer model [
        <xref ref-type="bibr" rid="ref18">18</xref>
        ].
      </p>
      <p>The goal of our work is to close this gap for one of the directions of text style transfer, namely
detoxification. We collect a parallel dataset via crowdsourcing. We ask crowd workers to
rewrite the toxic sentences in a non-toxic way and employ other workers to verify the rewritten
versions. We ask several workers to paraphrase each of the toxic messages and yield multiple
paraphrases.</p>
      <p>Our main contribution is a new crowdsourcing setup for collecting parallel data for style
transfer tasks (in our case — for detoxification task). We also release a collected parallel dataset. 1</p>
    </sec>
    <sec id="sec-2">
      <title>2. Related Work</title>
      <p>Here we discuss the approaches to creating training data for style transfer and, in particular, for
detoxification task.</p>
      <sec id="sec-2-1">
        <title>2.1. Style Transfer Datasets</title>
        <p>
          The vast majority of datasets for style transfer are non-parallel. Thus, they consist of two or
more subcorpora of a particular style. The subcorpora are not related to one another. Collecting
such datasets is usually relatively easy because we do not need to label the texts for style
explicitly. The style labels often already exist in the data (as in case of positive and negative
reviews [
          <xref ref-type="bibr" rid="ref12">12</xref>
          ]2) or their source serves as a label (e.g. texts from Twitter can be labelled with
“Twitter” style, scientific articles get a label “academic”, etc.). In these cases, data collection boils
down to fetching the texts from the original sources, and the corpus size depends solely on the
number of texts in these sources. A more complicated scenario is required when “style” is not
a property of the data source. In the case of corpora labelled for toxicity, each text has to be
manually labelled for the presence or absence of toxic content. However, even in this case, it is
possible to collect a large number of texts — the size of the first Jigsaw dataset [
          <xref ref-type="bibr" rid="ref19">19</xref>
          ] contains
140,000 sentences, and the aggregated size of three Jigsaw datasets [
          <xref ref-type="bibr" rid="ref19 ref20 ref21">19, 20, 21</xref>
          ] is around 2
million unique entities.
        </p>
        <p>
          In contrast to that, parallel corpora are more dificult to generate. For some other tasks, the
parallel data may appear naturally, so that researchers do not need to perform “translation”
for the research purposes. For example, translations between languages are generated simply
because there is a need to transfer the information to people who do not speak the source
language. Similarly, the summarization task can use abstracts of scientific papers [
          <xref ref-type="bibr" rid="ref22">22</xref>
          ], “TL;DR”
1https://github.com/skoltech-nlp/parallel_detoxification_dataset
2https://github.com/lijuncen/Sentiment-and-Style-Transfer
sections of social media posts [
          <xref ref-type="bibr" rid="ref23">23</xref>
          ] and summaries of news articles [
          <xref ref-type="bibr" rid="ref24">24</xref>
          ], which are created for
convenience and not solely for textual data collection. There exist examples of naturally created
parallel style transfer datasets. One of them is the Bible dataset [
          <xref ref-type="bibr" rid="ref17">17</xref>
          ] which exists in multiple
translations of diferent epochs. Another example is the simple-to-regular Wikipedia dataset [
          <xref ref-type="bibr" rid="ref25">25</xref>
          ]
which was generated automatically by aligning the text of Wikipedia with that of Simple
Wikipedia. Likewise, a biased-to-neutral Wikipedia corpus [
          <xref ref-type="bibr" rid="ref26">26</xref>
          ] was created automatically using
the information on article edits.
        </p>
        <p>
          Besides these special cases, there exists a large style transfer dataset that was created from
scratch. This is GYAFC dataset [
          <xref ref-type="bibr" rid="ref14">14</xref>
          ] which contains informal sentences and their formal versions
written by crowd workers and reviewed by experts. They used Amazon Mechanical Turk to
collect the data. The task was only to generate the paraphrasing and the quality control was
done manually. We suggest a new pipeline that does not require manual selection of samples
for the dataset and provide automatic control of the quality.
        </p>
      </sec>
      <sec id="sec-2-2">
        <title>2.2. Toxicity Datasets</title>
        <p>
          There exist a large number of datasets labelled for toxicity. They contain sentences and
paragraphs from various social media such as Twitter [
          <xref ref-type="bibr" rid="ref27 ref6 ref7">6, 27, 7</xref>
          ], Reddit [
          <xref ref-type="bibr" rid="ref28 ref29">28, 29</xref>
          ], Facebook [
          <xref ref-type="bibr" rid="ref30">30</xref>
          ]. There
exist a number of datasets based on Wikipedia talk pages — namely, Jigsaw datasets [
          <xref ref-type="bibr" rid="ref19 ref20 ref21">19, 20, 21</xref>
          ]
and some others [
          <xref ref-type="bibr" rid="ref8">8</xref>
          ]. The majority of data is labelled via crowdsourcing, except for several
expert-labelled corpora [
          <xref ref-type="bibr" rid="ref6">6</xref>
          ]. The labels usually include several varieties of toxicity, for example,
they diferentiate between ofence and hate speech [
          <xref ref-type="bibr" rid="ref27 ref7">27, 7</xref>
          ]. Some datasets are restricted to a
particular type of toxicity, e.g. sexism and racism [
          <xref ref-type="bibr" rid="ref6 ref7">6, 7</xref>
          ] or explore a particular type of toxicity,
for example, toxic unanswerable questions [
          <xref ref-type="bibr" rid="ref29">29</xref>
          ]. The size of the datasets ranges from 9,000 [
          <xref ref-type="bibr" rid="ref7">7</xref>
          ]
to 100,000 sentences [
          <xref ref-type="bibr" rid="ref8">8</xref>
          ], of which toxic sentences usually constitute 25–30%.
        </p>
        <p>
          None of these datasets is parallel, because they were created for toxicity classification, and
not for rewriting of toxic sentences. However, in works on text detoxification, the authors use
these datasets either directly for training their models or to train classifiers which are then
used for automatically labelling more data with (toxic or neutral) style. Nogueira dos Santos et
al. [
          <xref ref-type="bibr" rid="ref9">9</xref>
          ] use the Reddit and Twitter corpora automatically labelled for toxicity using a pre-trained
classifier. Tran et al. [
          <xref ref-type="bibr" rid="ref10">10</xref>
          ] collect a subset of controversial Reddit comments and label them
automatically based on the presence or absence of ofensive words from a manually constructed
list. In the work [
          <xref ref-type="bibr" rid="ref11">11</xref>
          ] the authors use the only large dataset with manual toxicity labelling,
namely, the Jigsaw dataset used in the competition of fighting the Unintended bias in toxicity
detection [
          <xref ref-type="bibr" rid="ref20">20</xref>
          ]. Similarly to this work, we employ one of the Jigsaw datasets. However, our
work is the first to create a parallel detoxification corpus.
        </p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>3. Paraphrase Generation Pipeline</title>
      <p>
        We ask crowd workers to rewrite toxic sentences so that they keep the original content and do
not sound ofensive. We hire workers via Yandex.Toloka 3 platform. Since the phrases produced
by crowd workers can be of low quality, they should not be used without revision. In [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ] this
Reddit&amp;Twitter +
Jigsaw Datasets
      </p>
      <p>.
...</p>
      <p>.
.
.</p>
      <p>Toxicity
classifier</p>
      <p>Toxic
Sentence
If 2/3 annotators
agree</p>
      <p>Task 1: Rewrite the text
in a polite way
Is it possible?
No</p>
      <p>Yes
Non-Toxic
Paraphrase</p>
      <p>Task m2:eDano tthheesseamseen?tences
SeTnotxeincce PNaoranp-Thorxaisce</p>
      <p>No</p>
      <p>Yes</p>
      <p>Yes
Task 3: Is this sentence
toxic?
Non-Toxic
Paraphrase</p>
      <p>No
revision was conducted by experts. We suggest an alternative setup where sentences are also
verified by (other) crowd workers.</p>
      <p>The objective of detoxification is to rephrase a toxic sentence so that (i) it keeps the original
content and (ii) stops being toxic. Thus, we create three crowdsourcing projects: one for
collecting paraphrases and another two for checking if these paraphrases conform to the two
objectives. We apply the three tasks to the data sequentially. The overall pipeline is shown in
Figure 1.</p>
      <sec id="sec-3-1">
        <title>3.1. Task 1: Generation</title>
        <p>In the first task, we ask users to rephrase a given sentence so that it does not sound ofensive.
Workers are shown a phrase and should rewrite them in a textbox (see Figure 2a).</p>
        <p>However, not all sentences can be detoxified. First, there exist sentences that do not contain
any non-toxic content — so removing toxicity from them would leave nothing from the original
sentences. Consider the following examples:
• It sucks that you’re an awful person,
• Maybe they should deport you back to your country, or your grandparents country.</p>
        <p>Their only content is an ofence towards the reader, so if we detoxify them, their sense will
difer substantially.</p>
        <p>Secondly, since we pre-select sentences for detoxification semi-automatically (see Section 4.1),
some of the input sentences can be non-toxic and need no detoxification. Finally, some of the
given sentences can be unclear to workers due to lack of context or simply because they are
meaningless.</p>
        <p>If we do not give the worker the possibility to skip a sentence without providing a paraphrase,
we can yield a large number of bad-quality paraphrases. Therefore, we extend the task interface
with the option “I can’t rewrite the text”. When a user chooses it, they are shown the possible
reasons for the inability to rewrite (see Figure 2b).</p>
        <p>On the other hand, some workers can use the “I can’t rewrite” option to cheat. Since choosing
this option is faster than rewriting a sentence, they can choose it too often. To avoid that, we
give each input sentence to three workers and pay them for choosing the “I can’t rewrite” option
only if two or more of them agree on it. Otherwise, if a worker submits a paraphrase, we check
it manually in Tasks 2 and 3 and pay only for the paraphrases approved during both tasks.
(a) Generation of paraphrases.
(b) Reasons of inability to rewrite.</p>
      </sec>
      <sec id="sec-3-2">
        <title>3.2. Task 2: Content Preservation Check</title>
        <p>After having generated the paraphrases, we show them to users along with the original messages
and ask if the meanings of the two sentences are close. This procedure checks if the content was
preserved in the detoxified version of the input sentence and also implicitly filters out senseless
outputs because they obviously do not keep the original content. The task interface is shown in
Figure 3.</p>
      </sec>
      <sec id="sec-3-3">
        <title>3.3. Task 3: Toxicity Check</title>
        <p>The second series of paraphrases review checks if the workers succeeded in eliminating toxicity.
We show users the paraphrases and ask if they contain any ofence or swear words (see Figure 4).</p>
        <p>Besides filtering out unsuitable paraphrases, Tasks 2 and 3 serve for paying for work done in
Task 1. Namely, we only pay for paraphrases which the checks in Tasks 2 and 3.</p>
        <p>The overall data collection pipeline is the following:
• We select sentences for rewriting,
• We feed the sentences to Task 1,
• We feed the paraphrases generated in Task 1 to Task 2,
• We feed the paraphrases which passed Task 2 to Task 3,
• We pay for paraphrases from Task 1, if they passed checks in Task 2 and Task 3,
• We pay for “I can’t rewrite” answers if two or more workers agreed on them.</p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>4. Crowdsourcing Settings</title>
      <p>Here we describe the settings of our crowdsourcing projects in more detail.</p>
      <sec id="sec-4-1">
        <title>4.1. Data Preprocessing</title>
        <p>
          We fetch data for manual rewriting from two sources: (i) Jigsaw dataset of toxic sentences [
          <xref ref-type="bibr" rid="ref19">19</xref>
          ],
and (ii) Reddit&amp;Twitter dataset used by [
          <xref ref-type="bibr" rid="ref9">9</xref>
          ].
        </p>
        <p>
          The Reddit&amp;Twitter dataset was pre-processed by the authors [
          <xref ref-type="bibr" rid="ref9">9</xref>
          ]. This preprocessing included
dividing original comments into sentences and automatically classifying them as toxic or
nontoxic with a pre-trained classifier. The reason for this is that the original comments can be long,
and generation models perform worse on longer texts. We use this Reddit&amp;Twitter data and
perform the analogous preprocessing for the Jigsaw dataset: we divide it into sentences and
classify them with a pre-trained toxicity classifier.
        </p>
        <p>
          To train a classifier, we merge the English parts of the three datasets by Jigsaw [
          <xref ref-type="bibr" rid="ref19 ref20 ref21">19, 20, 21</xref>
          ],
containing around 2 million examples. We take half of this merged dataset and fine-tune a
RoBERTa model [
          <xref ref-type="bibr" rid="ref31">31</xref>
          ] on it. We use the roberta-large model from the original repository.
The classifier reaching the AUC-ROC of 0.98 and F 1-score of 0.76 on the test set of the first
Jigsaw dataset.
        </p>
        <p>We select only sentences classified as toxic, whose length is between 5 and 20 words (for
both datasets). The lower length limit serves for filtering out overly short sentences which are
dificult to understand without context. The upper limit is for the convenience of workers who
struggle with the rewriting of long sentences.</p>
      </sec>
      <sec id="sec-4-2">
        <title>4.2. Multiple Labellings</title>
        <p>
          We ask several workers to label each example. For Tasks 2 and 3, we compute the final label
using the Dawid-Skene aggregation method [
          <xref ref-type="bibr" rid="ref32">32</xref>
          ] which defines the true label iteratively giving
more weight to the answers of workers whose opinion more often agrees with that of other
workers.
        </p>
        <p>In Task 1 the number of labellings per task is 3. In Tasks 2 and 3, the number of labellings
per task is defined dynamically depending on the agreement on the task. First, the minimum
number of users (3 in our setting) label an example, and if their agreement is above a threshold
(0.8 in our setting), the task is not sent to extra labelling. Otherwise, the system fetches up to
the maximum number of labellings (5 in our setting) until the agreement reaches the threshold.</p>
      </sec>
      <sec id="sec-4-3">
        <title>4.3. Instructions</title>
        <p>The instruction for crowd workers says that they should rewrite the given sentences so that
they mean the same as the original ones, but do not sound ofensive anymore. We do not
explicitly define the notion of ofensiveness, because we suggest that it should be an intuitively
clear concept. Instead of giving a definition of toxicity, we give examples of toxic and non-toxic
sentences.</p>
      </sec>
      <sec id="sec-4-4">
        <title>4.4. Training of Workers</title>
        <p>For all tasks, workers have to complete a set of training tasks to be admitted to work on paid
tasks. These tasks have a pre-defined correct answer. If a user answer does not match the
correct one, the user is shown a hint which explains their mistake. Workers are admitted to the
paid task if they completed the training with a score above a threshold: 40% correct answers for
Task 1, 90% for Tasks 2 and 3. Such low acceptance score for Task 1 is due to the task complexity
– there is no single answer whether the sentence can be rewritten into a civil manner or not
because diferent people from diferent cultural background can have diferent perspective on
the toxicity. At the same time, even such a low score allows us to ban the user that just select
only one answer, for example, and do not put efort into thorough task completeness. Task 2
and 3 have more exact answer and, as a result, have a higher threshold of acceptance.</p>
        <p>In addition to that, we provide extra training tasks during labelling. Training tasks are added
to labelling examples. If a worker makes an error in such tasks, they are shown an explanation.
Workers are not penalised for making errors. We need these tasks to reinforce the worker’s
understanding of the task.</p>
      </sec>
      <sec id="sec-4-5">
        <title>4.5. Quality Control</title>
        <p>To control the quality, we occasionally add control tasks during labelling. These tasks have
a pre-defined correct answer. If a worker makes too many mistakes in these tasks, they are
banned. In our projects, a worker is banned if they make 3 or more mistakes in the latest 4
control tasks.</p>
        <p>Another means of control that we use is the agreement between users. If a user disagrees
with the majority (3 or more) of users in over 66% cases, this user is banned.</p>
      </sec>
      <sec id="sec-4-6">
        <title>4.6. Payment</title>
        <p>In Yandex.Toloka, a task page shown to workers can contain multiple tasks. Therefore, customers
set the payment per task page. In Task 1, a page contains 4 tasks for labelling and one control
task and costs $0.02. In Tasks 2 and 3, a page consists of 10 labelling tasks, 1 to 2 training tasks
and 1 to 2 control tasks and costs $0.01. The number of training and control tasks is defined by
the agreement of the worker with others.</p>
        <p>Tasks 2 and 3 are paid instantly, whereas in Task 1 we check the paraphrases before paying.
If a worker indicated that a sentence cannot be paraphrased, we pay for this answer only if at
least one other worker agreed with that. If a worker typed in a paraphrase, we send it to Tasks
2 and 3 and pay only for the ones approved by both tasks. The payment procedure is shown in</p>
        <sec id="sec-4-6-1">
          <title>Paraphrase</title>
          <p>this is scaring the shit out of me.
this is a joke , are you all fucking retards?
everybody is such a fucking pussy.</p>
        </sec>
        <sec id="sec-4-6-2">
          <title>This is really scaring me.</title>
        </sec>
        <sec id="sec-4-6-3">
          <title>This is a joke, are you all crazy?</title>
        </sec>
        <sec id="sec-4-6-4">
          <title>Everybody is acting cowardly.</title>
          <p>did you think i was going to sit back and let some
imbecile spew hatred towards me?</p>
        </sec>
        <sec id="sec-4-6-5">
          <title>Did you think I was going to let</title>
          <p>an unreasonable person hate me?
calm the fuck down, cnn.</p>
        </sec>
        <sec id="sec-4-6-6">
          <title>Please calm your nerves, CNN.</title>
          <p>why is the scale of that graph so fucked up?</p>
        </sec>
        <sec id="sec-4-6-7">
          <title>Why is the scale of that graph not placed rightly.</title>
          <p>Reddit
Jigsaw
the chinese came out of this looking like lying,
petulant children.</p>
        </sec>
        <sec id="sec-4-6-8">
          <title>The chinese came out of this looking like</title>
          <p>dishonest, bad tempered children.
all you trump clowns are seriously messed up.
Trumps voters are seriously mislead.
youre a libby so dont talk ridiculous
like you would vote any other way.
she is a lying disgrace who refuses
to accept that she lost.
if you think so, you are making a clown
out of yourself.</p>
        </sec>
      </sec>
    </sec>
    <sec id="sec-5">
      <title>5. Data and Pipeline Analysis</title>
      <p>We tested a pipeline for collecting parallel detoxification data. As a proof of concept, we
collected a dataset with paraphrases for 1,244 toxic sentences, each having 1-5 paraphrase
variants, resulting in 5,228 paraphrases overall. The examples of generated paraphrases are
given in Table 1.</p>
      <sec id="sec-5-1">
        <title>5.1. Data Statistics</title>
        <p>The statistics of the paraphrases written by crowd workers are presented in Table 2. For both
Jigsaw and Reddit&amp;Twitter datasets, we used the equal number of sentences (1,200) as the input
to the crowdsourcing pipeline from Figure 1. From this input data, 675 samples from Jigsaw
(56%) received at least one good paraphrase, while for the Reddit dataset this amount is smaller
— 569 samples (47%).</p>
        <p>Some of the input samples could not be paraphrased or all paraphrases generated for them
were rejected during verification. Others yielded one or more paraphrases. The distribution
of the diferent results is shown in Figure 5. The pictures for Jigsaw and Reddit datasets difer.
Besides the mentioned diference in the number of input samples which received paraphrases,
Reddit has a larger number of sentences with more than one paraphrase. These sentences are
probably easier to detoxify because multiple workers succeeded in providing paraphrases for
them. Reddit has more of such sentences. The annotators consistency is quite high (Table 2,
columns 6 and 7). For Task2 and Task3 for both datasets ≥ 92% of all marked up samples have
the confidence in the decision of ≥ 90%. We compute the cost of manual annotation. The cost
per input sample is the cost of generating 1-5 paraphrases for the sample and checking these
paraphrases for toxicity and content matching. The cost of the final sentence pair includes
the cost of processing the inputs for which no good paraphrases were generated. Thus, this
parameter depends not only on crowdsourcing settings but also on the dataset, because the
percentage of detoxifiable sentences may vary for diferent data sources.</p>
        <p>Multiple paraphrases can give us a better insight into the phenomenon of toxicity. Namely, by
comparing multiple paraphrases of one sentence we can detect its toxicity regions with higher
confidence. While a single paraphrase can be uninformative (e.g. it can fully rephrase a sentence
where toxicity could be eliminated by replacing several words), multiple paraphrases show a
more objective picture. Table 3 shows examples of such cases. The colour is brighter for words
to think that she’s been doing that kind of shit for yeaaaars
her behaviour has been constant for years.
to think that she’s been doing that kind of thing for years.</p>
        <p>to think that she’s been doing that for years.</p>
        <sec id="sec-5-1-1">
          <title>Paraphrase to think she’s been doing that for years. to think that she’s been doing this kind of thing for years she is been doing those things for years to think that she’s been doing it for years.</title>
          <p>this is why the country is fucked up.
this is why the country does not going well.
this is why the country is not growing
country is sufering because of this
this is why the country is bad.</p>
          <p>this is why this country is messed up.</p>
        </sec>
        <sec id="sec-5-1-2">
          <title>Paraphrase that’s why the country is lost</title>
          <p>that’s why this country is in such a mess.
this country is bad
this may be the reason why our country is not so progressive
this is why the country isn’t developing.</p>
          <p>
            this is why the county has problems.
that are absent in the detoxified versions more often. It can be seen that while some non-toxic
words can occasionally be removed, the joint statistics of multiple paraphrases identifies the
regions of toxicity. This token-level information can be useful for toxicity classification as well.
As shown in [
            <xref ref-type="bibr" rid="ref33">33</xref>
            ], the rationales (highlighted phrases that justify the class label assigned to a
sentence) improve the performance of text classifiers and their explainability. The token-level
degree of toxicity can serve as a rationale for sentence-level classifiers.
          </p>
          <p>Also, it can be seen from Tables 1 and 3 that there can be some grammatical mistakes in both
original and generated sentences. The reason for that is that the majority of English content in
the Internet is produced by people for whom English is a second language. The same situation
about language we have for the annotators in our task. So, we consider these mistakes as natural
for both original and detoxified sentences.</p>
        </sec>
      </sec>
      <sec id="sec-5-2">
        <title>5.2. Crowdsourcers Performance</title>
        <p>Throughout data collection, up to 2,000 crowd workers participated in our experiments (in each
task). However, around 1/2 (Tasks 2 and 3) to 3/4 (Task 1) of them were banned for cheating
(too fast answers, failed captcha checks, errors in control questions).</p>
        <p>
          We can measure the performance of crowd workers with a number of parameters. These are
their agreement computed as the average confidence computed with Dawid-Skene aggregation
method [
          <xref ref-type="bibr" rid="ref32">32</xref>
          ] and their performance on pre-labelling training and control tasks. In the most
challenging Task 1 the performance on the control questions was 32.8% of correct answers. In
Tasks 2 and 3 these numbers were 63.4% and 86.9%, respectively. Thus, Task 3 was the easiest.
        </p>
        <p>This is corroborated by the fact that users completed this task faster. It took them on average
1 minute 31 seconds to label 13-15 sentences (one task page) as toxic or safe. For Task 2 this
number is 3 minutes 8 seconds (for 13-15 tasks), and one Task 1 page was completed on average
in 5 minutes 17 seconds (5 tasks).</p>
        <p>In addition to that, Task 3 was rated higher by crowd workers than the other two tasks. In
Yandex.Toloka workers can rate projects by four parameters:
• how interesting the task is (formulated as “Would you complete this task in the future?”),
• clarity of instructions,
• task interface,
• communication with the requester.</p>
        <p>Task 3 got an average score of 4.77, whereas Tasks 1 and 2 got scores of 4.51 and 4.64,
respectively.</p>
      </sec>
    </sec>
    <sec id="sec-6">
      <title>6. Conclusions and Future Work</title>
      <p>We describe a crowdsourcing setup for the collection of parallel data for the detoxification task.
The data consists of pairs of sentences, one of them is toxic, and the other one has the same
meaning but is not ofensive. In our setup workers write paraphrases for toxic sentences and
verify the content preservation and the absence of toxicity.</p>
      <p>We collected 1-5 manually written paraphrases for over 1,200 toxic sentences from Reddit,
Twitter, and Wikipedia discussion pages. This corpus is relatively small. However, we believe
that even this dataset can be used for supervised training of a detoxification model, for example,
for fine-tuning of a large language model, such as GPT-2 [ 34] or T5 [35]. Besides, it can be
used for the training of a token-level toxicity classifier and as a source of extra information in a
sentence-level toxicity classifier.</p>
      <p>The most evident direction of future work is the collection of a larger dataset and investigation
of the optimal number of parallel examples for the training of a well-performing detoxification
model. In addition to that, we would like to further improve our crowdsourcing pipeline by
ifnding the optimal number of labellings per sample and compare the cost and eficiency of
setups with one and multiple paraphrases.</p>
      <p>We would also like to further research the usefulness of multiple paraphrases for a single
toxic message for the training and evaluation of detoxification models. Finally, our experiments
show that data from diferent sources can have diferent properties important for parallel data
collection. Namely, the Reddit dataset has more sentences that can be paraphrased. It would be
useful for further data collection to investigate the properties of diferent datasets.
benchmark dataset for explainable hate speech detection, in: Thirty-Fifth AAAI Conference
on Artificial Intelligence, AAAI 2021, Thirty-Third Conference on Innovative Applications
of Artificial Intelligence, IAAI 2021, The Eleventh Symposium on Educational Advances in
Artificial Intelligence, EAAI 2021, Virtual Event, February 2-9, 2021, AAAI Press, 2021, pp.
14867–14875. URL: https://ojs.aaai.org/index.php/AAAI/article/view/17745.
[34] A. Radford, J. Wu, R. Child, D. Luan, D. Amodei, I. Sutskever, Language models are
unsupervised multitask learners, OpenAI blog 1 (2019) 9.
[35] C. Rafel, N. Shazeer, A. Roberts, K. Lee, S. Narang, M. Matena, Y. Zhou, W. Li, P. J. Liu,
Exploring the limits of transfer learning with a unified text-to-text transformer, Journal of
Machine Learning Research 21 (2020) 1–67. URL: http://jmlr.org/papers/v21/20-074.html.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>M.</given-names>
            <surname>Zampieri</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Nakov</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Rosenthal</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Atanasova</surname>
          </string-name>
          , G. Karadzhov,
          <string-name>
            <given-names>H.</given-names>
            <surname>Mubarak</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Derczynski</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Z.</given-names>
            <surname>Pitenis</surname>
          </string-name>
          , Ç. Çöltekin, SemEval-2020 task 12:
          <article-title>Multilingual ofensive language identification in social media (OfensEval 2020)</article-title>
          ,
          <source>in: Proceedings of the Fourteenth Workshop on Semantic Evaluation</source>
          , International Committee for Computational Linguistics,
          <source>Barcelona (online)</source>
          ,
          <year>2020</year>
          , pp.
          <fpage>1425</fpage>
          -
          <lpage>1447</lpage>
          . URL: https://www.aclweb.org/anthology/2020.semeval-
          <volume>1</volume>
          .
          <fpage>188</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <surname>A. G. D'Sa</surname>
            ,
            <given-names>I.</given-names>
          </string-name>
          <string-name>
            <surname>Illina</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          <string-name>
            <surname>Fohr</surname>
          </string-name>
          ,
          <article-title>Towards non-toxic landscapes: Automatic toxic comment detection using DNN</article-title>
          , in: Proceedings of the Second Workshop on Trolling, Aggression and Cyberbullying,
          <source>European Language Resources Association (ELRA)</source>
          , Marseille, France,
          <year>2020</year>
          , pp.
          <fpage>21</fpage>
          -
          <lpage>25</lpage>
          . URL: https://www.aclweb.org/anthology/2020.trac-
          <volume>1</volume>
          .4.
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>X.</given-names>
            <surname>Han</surname>
          </string-name>
          ,
          <string-name>
            <surname>Y</surname>
          </string-name>
          . Tsvetkov,
          <article-title>Fortifying toxic speech detectors against veiled toxicity</article-title>
          ,
          <source>in: Proceedings of the 2020 Conference on Empirical Methods in Natural Language Processing (EMNLP)</source>
          ,
          <article-title>Association for Computational Linguistics</article-title>
          , Online,
          <year>2020</year>
          , pp.
          <fpage>7732</fpage>
          -
          <lpage>7739</lpage>
          . URL: https://www.aclweb.org/anthology/2020.emnlp-main.
          <volume>622</volume>
          . doi:
          <volume>10</volume>
          .18653/v1/
          <year>2020</year>
          . emnlp-main.
          <volume>622</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>A.</given-names>
            <surname>Schmidt</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Wiegand</surname>
          </string-name>
          ,
          <article-title>A survey on hate speech detection using natural language processing</article-title>
          ,
          <source>in: Proceedings of the Fifth International Workshop on Natural Language Processing for Social Media</source>
          , Association for Computational Linguistics, Valencia, Spain,
          <year>2017</year>
          , pp.
          <fpage>1</fpage>
          -
          <lpage>10</lpage>
          . URL: https://aclanthology.org/W17-1101. doi:
          <volume>10</volume>
          .18653/v1/
          <fpage>W17</fpage>
          -1101.
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>A.</given-names>
            <surname>Pelicon</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Shekhar</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Martinc</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Škrlj</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Purver</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Pollak</surname>
          </string-name>
          ,
          <article-title>Zero-shot crosslingual content filtering: Ofensive language and hate speech detection</article-title>
          ,
          <source>in: Proceedings of the EACL Hackashop on News Media Content Analysis and Automated Report Generation, Association for Computational Linguistics</source>
          , Online,
          <year>2021</year>
          , pp.
          <fpage>30</fpage>
          -
          <lpage>34</lpage>
          . URL: https://aclanthology.org/
          <year>2021</year>
          .hackashop-
          <volume>1</volume>
          .5.
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <given-names>Z.</given-names>
            <surname>Waseem</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Hovy</surname>
          </string-name>
          ,
          <article-title>Hateful symbols or hateful people? predictive features for hate speech detection on Twitter</article-title>
          ,
          <source>in: Proceedings of the NAACL Student Research Workshop</source>
          , Association for Computational Linguistics, San Diego, California,
          <year>2016</year>
          , pp.
          <fpage>88</fpage>
          -
          <lpage>93</lpage>
          . URL: https://aclanthology.org/N16-2013. doi:
          <volume>10</volume>
          .18653/v1/
          <fpage>N16</fpage>
          -2013.
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <given-names>V.</given-names>
            <surname>Basile</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Bosco</surname>
          </string-name>
          ,
          <string-name>
            <given-names>E.</given-names>
            <surname>Fersini</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Nozza</surname>
          </string-name>
          ,
          <string-name>
            <given-names>V.</given-names>
            <surname>Patti</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F. M.</given-names>
            <surname>Rangel Pardo</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Rosso</surname>
          </string-name>
          , M. Sanguinetti, SemEval
          <article-title>-2019 task 5: Multilingual detection of hate speech against immigrants and women in Twitter</article-title>
          ,
          <source>in: Proceedings of the 13th International Workshop on Semantic Evaluation</source>
          ,
          <article-title>Association for Computational Linguistics</article-title>
          , Minneapolis, Minnesota, USA,
          <year>2019</year>
          , pp.
          <fpage>54</fpage>
          -
          <lpage>63</lpage>
          . URL: https://aclanthology.org/S19-2007. doi:
          <volume>10</volume>
          .18653/v1/
          <fpage>S19</fpage>
          -2007.
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <given-names>E.</given-names>
            <surname>Brassard-Gourdeau</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Khoury</surname>
          </string-name>
          ,
          <article-title>Subversive toxicity detection using sentiment information</article-title>
          ,
          <source>in: Proceedings of the Third Workshop on Abusive Language Online</source>
          , Association for Computational Linguistics, Florence, Italy,
          <year>2019</year>
          , pp.
          <fpage>1</fpage>
          -
          <lpage>10</lpage>
          . URL: https: //aclanthology.org/W19-3501. doi:
          <volume>10</volume>
          .18653/v1/
          <fpage>W19</fpage>
          -3501.
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <surname>C.</surname>
          </string-name>
          <article-title>Nogueira dos Santos, I. Melnyk, I. Padhi, Fighting ofensive language on social media with unsupervised text style transfer</article-title>
          ,
          <source>in: Proceedings of the 56th Annual Meeting of the Association for Computational Linguistics (Volume</source>
          <volume>2</volume>
          :
          <string-name>
            <surname>Short</surname>
            <given-names>Papers)</given-names>
          </string-name>
          ,
          <source>Association for Computational Linguistics</source>
          , Melbourne, Australia,
          <year>2018</year>
          , pp.
          <fpage>189</fpage>
          -
          <lpage>194</lpage>
          . URL: https:// aclanthology.org/P18-2031. doi:
          <volume>10</volume>
          .18653/v1/
          <fpage>P18</fpage>
          -2031.
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <given-names>M.</given-names>
            <surname>Tran</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Zhang</surname>
          </string-name>
          , M. Soleymani,
          <article-title>Towards a friendly online community: An unsupervised style transfer framework for profanity redaction</article-title>
          ,
          <source>in: Proceedings of the 28th International Conference on Computational Linguistics</source>
          ,
          <source>International Committee on Computational Linguistics</source>
          , Barcelona,
          <source>Spain (Online)</source>
          ,
          <year>2020</year>
          , pp.
          <fpage>2107</fpage>
          -
          <lpage>2114</lpage>
          . URL: https://aclanthology.org/
          <year>2020</year>
          .coling-main.
          <volume>190</volume>
          . doi:
          <volume>10</volume>
          .18653/v1/
          <year>2020</year>
          .coling-main.
          <volume>190</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [11]
          <string-name>
            <given-names>L.</given-names>
            <surname>Laugier</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Pavlopoulos</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Sorensen</surname>
          </string-name>
          , L. Dixon,
          <article-title>Civil rephrases of toxic texts with self-supervised transformers</article-title>
          ,
          <source>in: Proceedings of the 16th Conference of the European Chapter of the Association for Computational Linguistics:</source>
          Main Volume,
          <article-title>Association for Computational Linguistics</article-title>
          , Online,
          <year>2021</year>
          , pp.
          <fpage>1442</fpage>
          -
          <lpage>1461</lpage>
          . URL: https://aclanthology.org/
          <year>2021</year>
          .eacl-main.
          <volume>124</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          [12]
          <string-name>
            <given-names>J.</given-names>
            <surname>Li</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Jia</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            <surname>He</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Liang</surname>
          </string-name>
          , Delete, retrieve, generate
          <article-title>: a simple approach to sentiment and style transfer</article-title>
          ,
          <source>in: Proceedings of the 2018 Conference of the North American Chapter of the Association for Computational Linguistics: Human Language Technologies</source>
          , Volume
          <volume>1</volume>
          (
          <string-name>
            <surname>Long</surname>
            <given-names>Papers)</given-names>
          </string-name>
          ,
          <source>Association for Computational Linguistics</source>
          , New Orleans, Louisiana,
          <year>2018</year>
          , pp.
          <fpage>1865</fpage>
          -
          <lpage>1874</lpage>
          . URL: https://aclanthology.org/N18-1169. doi:
          <volume>10</volume>
          .18653/v1/
          <fpage>N18</fpage>
          -1169.
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          [13]
          <string-name>
            <given-names>K.</given-names>
            <surname>Chawla</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B. V.</given-names>
            <surname>Srinivasan</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Chhaya</surname>
          </string-name>
          ,
          <article-title>Generating formality-tuned summaries using input-dependent rewards</article-title>
          ,
          <source>in: Proceedings of the 23rd Conference on Computational Natural Language Learning (CoNLL)</source>
          ,
          <article-title>Association for Computational Linguistics</article-title>
          , Hong Kong, China,
          <year>2019</year>
          , pp.
          <fpage>833</fpage>
          -
          <lpage>842</lpage>
          . URL: https://aclanthology.org/K19-1078. doi:
          <volume>10</volume>
          .18653/ v1/
          <fpage>K19</fpage>
          -1078.
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          [14]
          <string-name>
            <given-names>S.</given-names>
            <surname>Rao</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Tetreault</surname>
          </string-name>
          ,
          <article-title>Dear sir or madam, may I introduce the GYAFC dataset: Corpus, benchmarks and metrics for formality style transfer</article-title>
          ,
          <source>in: Proceedings of the 2018 Conference of the North American Chapter of the Association for Computational Linguistics: Human Language Technologies</source>
          , Volume
          <volume>1</volume>
          (
          <string-name>
            <surname>Long</surname>
            <given-names>Papers)</given-names>
          </string-name>
          ,
          <source>Association for Computational Linguistics</source>
          , New Orleans, Louisiana,
          <year>2018</year>
          , pp.
          <fpage>129</fpage>
          -
          <lpage>140</lpage>
          . URL: https://aclanthology.org/N18-1012. doi:
          <volume>10</volume>
          .18653/v1/
          <fpage>N18</fpage>
          -1012.
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          [15]
          <string-name>
            <given-names>C.</given-names>
            <surname>Danescu-Niculescu-Mizil</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Sudhof</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Jurafsky</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Leskovec</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Potts</surname>
          </string-name>
          ,
          <article-title>A computational approach to politeness with application to social factors, in: Proceedings of the 51st Annual Meeting of the Association for Computational Linguistics</article-title>
          (Volume
          <volume>1</volume>
          :
          <string-name>
            <surname>Long</surname>
            <given-names>Papers)</given-names>
          </string-name>
          ,
          <source>Association for Computational Linguistics</source>
          , Sofia, Bulgaria,
          <year>2013</year>
          , pp.
          <fpage>250</fpage>
          -
          <lpage>259</lpage>
          . URL: https: //aclanthology.org/P13-1025.
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          [16]
          <string-name>
            <given-names>A.</given-names>
            <surname>Madaan</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Setlur</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Parekh</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Poczos</surname>
          </string-name>
          , G. Neubig,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Yang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Salakhutdinov</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A. W.</given-names>
            <surname>Black</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Prabhumoye</surname>
          </string-name>
          ,
          <article-title>Politeness transfer: A tag and generate approach, in: Proceedings of the 58th Annual Meeting of the Association for Computational Linguistics, Association for Computational Linguistics</article-title>
          , Online,
          <year>2020</year>
          , pp.
          <fpage>1869</fpage>
          -
          <lpage>1881</lpage>
          . URL: https://aclanthology.org/
          <year>2020</year>
          .acl-main.
          <volume>169</volume>
          . doi:
          <volume>10</volume>
          .18653/v1/
          <year>2020</year>
          .acl-main.
          <volume>169</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          [17]
          <string-name>
            <given-names>K.</given-names>
            <surname>Carlson</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Riddell</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Rockmore</surname>
          </string-name>
          ,
          <article-title>Evaluating prose style transfer with the bible</article-title>
          ,
          <source>Royal Society Open Science</source>
          <volume>5</volume>
          (
          <year>2018</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          [18]
          <string-name>
            <given-names>D.</given-names>
            <surname>Dementieva</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Moskovskiy</surname>
          </string-name>
          ,
          <string-name>
            <given-names>V.</given-names>
            <surname>Logacheva</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D. O.</given-names>
            <surname>Kozlova</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Semenov</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Panchenko</surname>
          </string-name>
          ,
          <article-title>Methods for detoxification of texts for the russian language</article-title>
          ,
          <source>in: Proceedings of the International Conference “Dialogue</source>
          <year>2021</year>
          ”, Moscow, Russia,
          <year>2021</year>
          . doi:
          <volume>99</volume>
          .9999/woot07-
          <fpage>S422</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          [19]
          <string-name>
            <surname>Jigsaw</surname>
          </string-name>
          ,
          <article-title>Toxic comment classification challenge</article-title>
          , https://www.kaggle.com/c/jigsaw-toxiccomment
          <article-title>-classification-</article-title>
          <string-name>
            <surname>challenge</surname>
          </string-name>
          ,
          <year>2018</year>
          . Accessed:
          <fpage>2021</fpage>
          -03-01.
        </mixed-citation>
      </ref>
      <ref id="ref20">
        <mixed-citation>
          [20]
          <string-name>
            <surname>Jigsaw</surname>
          </string-name>
          ,
          <article-title>Jigsaw unintended bias in toxicity classification</article-title>
          , https://www.kaggle.com/c/jigsawunintended
          <article-title>-bias-in-toxicity-</article-title>
          <string-name>
            <surname>classification</surname>
          </string-name>
          ,
          <year>2019</year>
          . Accessed:
          <fpage>2021</fpage>
          -03-01.
        </mixed-citation>
      </ref>
      <ref id="ref21">
        <mixed-citation>
          [21]
          <string-name>
            <surname>Jigsaw</surname>
          </string-name>
          ,
          <article-title>Jigsaw multilingual toxic comment classification</article-title>
          , https://www.kaggle.com/c/jigsawmultilingual-toxic
          <article-title>-comment-</article-title>
          <string-name>
            <surname>classification</surname>
          </string-name>
          ,
          <year>2020</year>
          . Accessed:
          <fpage>2021</fpage>
          -03-01.
        </mixed-citation>
      </ref>
      <ref id="ref22">
        <mixed-citation>
          [22]
          <string-name>
            <given-names>I.</given-names>
            <surname>Cachola</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Lo</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Cohan</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Weld</surname>
          </string-name>
          ,
          <article-title>TLDR: Extreme summarization of scientific documents, in: Findings of the Association for Computational Linguistics: EMNLP 2020, Association for Computational Linguistics</article-title>
          , Online,
          <year>2020</year>
          , pp.
          <fpage>4766</fpage>
          -
          <lpage>4777</lpage>
          . URL: https://aclanthology.org/
          <year>2020</year>
          .findings-emnlp.
          <volume>428</volume>
          . doi:
          <volume>10</volume>
          .18653/v1/
          <year>2020</year>
          .findings-emnlp.
          <volume>428</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref23">
        <mixed-citation>
          [23]
          <string-name>
            <given-names>M.</given-names>
            <surname>Völske</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Potthast</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Syed</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Stein</surname>
          </string-name>
          , TL;DR:
          <article-title>Mining Reddit to learn automatic summarization</article-title>
          ,
          <source>in: Proceedings of the Workshop on New Frontiers in Summarization, Association for Computational Linguistics</source>
          , Copenhagen, Denmark,
          <year>2017</year>
          , pp.
          <fpage>59</fpage>
          -
          <lpage>63</lpage>
          . URL: https://aclanthology.org/W17-4508. doi:
          <volume>10</volume>
          .18653/v1/
          <fpage>W17</fpage>
          -4508.
        </mixed-citation>
      </ref>
      <ref id="ref24">
        <mixed-citation>
          [24]
          <string-name>
            <surname>K. M. Hermann</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          <string-name>
            <surname>Kocisky</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          <string-name>
            <surname>Grefenstette</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          <string-name>
            <surname>Espeholt</surname>
            ,
            <given-names>W.</given-names>
          </string-name>
          <string-name>
            <surname>Kay</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          <string-name>
            <surname>Suleyman</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          <string-name>
            <surname>Blunsom</surname>
          </string-name>
          ,
          <article-title>Teaching machines to read and comprehend</article-title>
          , in: C.
          <string-name>
            <surname>Cortes</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          <string-name>
            <surname>Lawrence</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          <string-name>
            <surname>Lee</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          <string-name>
            <surname>Sugiyama</surname>
          </string-name>
          , R. Garnett (Eds.),
          <source>Advances in Neural Information Processing Systems</source>
          , volume
          <volume>28</volume>
          ,
          <string-name>
            <surname>Curran</surname>
            <given-names>Associates</given-names>
          </string-name>
          , Inc.,
          <year>2015</year>
          . URL: https://proceedings.neurips.cc/paper/2015/ ifle/afdec7005cc9f14302cd0474fd0f3c96-Paper.pdf.
        </mixed-citation>
      </ref>
      <ref id="ref25">
        <mixed-citation>
          [25]
          <string-name>
            <given-names>Z.</given-names>
            <surname>Zhu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Bernhard</surname>
          </string-name>
          ,
          <string-name>
            <surname>I. Gurevych</surname>
          </string-name>
          ,
          <article-title>A monolingual tree-based translation model for sentence simplification</article-title>
          ,
          <source>in: Proceedings of the 23rd International Conference on Computational Linguistics (Coling</source>
          <year>2010</year>
          ),
          <article-title>Coling 2010 Organizing Committee</article-title>
          , Beijing, China,
          <year>2010</year>
          , pp.
          <fpage>1353</fpage>
          -
          <lpage>1361</lpage>
          . URL: https://aclanthology.org/C10-1152.
        </mixed-citation>
      </ref>
      <ref id="ref26">
        <mixed-citation>
          [26]
          <string-name>
            <given-names>R.</given-names>
            <surname>Pryzant</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R. D.</given-names>
            <surname>Martinez</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Dass</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Kurohashi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Jurafsky</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Yang</surname>
          </string-name>
          ,
          <article-title>Automatically neutralizing subjective bias in text</article-title>
          ,
          <source>in: The Thirty-Fourth AAAI Conference on Artificial Intelligence</source>
          ,
          <source>AAAI</source>
          <year>2020</year>
          , The Thirty-Second
          <source>Innovative Applications of Artificial Intelligence Conference</source>
          ,
          <source>IAAI 2020, The Tenth AAAI Symposium on Educational Advances in Artificial Intelligence, EAAI</source>
          <year>2020</year>
          , New York, NY, USA, February 7-
          <issue>12</issue>
          ,
          <year>2020</year>
          , AAAI Press,
          <year>2020</year>
          , pp.
          <fpage>480</fpage>
          -
          <lpage>489</lpage>
          . URL: https://aaai.org/ojs/index.php/AAAI/article/view/5385.
        </mixed-citation>
      </ref>
      <ref id="ref27">
        <mixed-citation>
          [27]
          <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. W.</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 Eleventh International Conference on Web and Social Media</source>
          ,
          <string-name>
            <surname>ICWSM</surname>
          </string-name>
          <year>2017</year>
          , Montréal, Québec, Canada, May
          <volume>15</volume>
          -18,
          <year>2017</year>
          , AAAI Press,
          <year>2017</year>
          , pp.
          <fpage>512</fpage>
          -
          <lpage>515</lpage>
          . URL: https://aaai.org/ocs/index.php/ICWSM/ICWSM17/ paper/view/15665.
        </mixed-citation>
      </ref>
      <ref id="ref28">
        <mixed-citation>
          [28]
          <string-name>
            <given-names>J.</given-names>
            <surname>Kurrek</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H. M.</given-names>
            <surname>Saleem</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Ruths</surname>
          </string-name>
          ,
          <article-title>Towards a comprehensive taxonomy and large-scale annotated corpus for online slur usage</article-title>
          ,
          <source>in: Proceedings of the Fourth Workshop on Online Abuse and Harms</source>
          , Association for Computational Linguistics, Online,
          <year>2020</year>
          , pp.
          <fpage>138</fpage>
          -
          <lpage>149</lpage>
          . URL: https://aclanthology.org/
          <year>2020</year>
          .alw-
          <volume>1</volume>
          .17. doi:
          <volume>10</volume>
          .18653/v1/
          <year>2020</year>
          .alw-
          <volume>1</volume>
          .
          <fpage>17</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref29">
        <mixed-citation>
          [29]
          <string-name>
            <given-names>S.</given-names>
            <surname>Bagga</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Piper</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Ruths</surname>
          </string-name>
          , “
          <article-title>are you kidding me?”: Detecting unpalatable questions on Reddit, in: Proceedings of the 16th Conference of the European Chapter of the Association for Computational Linguistics: Main Volume, Association for Computational Linguistics</article-title>
          , Online,
          <year>2021</year>
          , pp.
          <fpage>2083</fpage>
          -
          <lpage>2099</lpage>
          . URL: https://aclanthology.org/
          <year>2021</year>
          .eacl-main.
          <volume>179</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref30">
        <mixed-citation>
          [30]
          <string-name>
            <given-names>R.</given-names>
            <surname>Kumar</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A. K.</given-names>
            <surname>Ojha</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Malmasi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Zampieri</surname>
          </string-name>
          ,
          <article-title>Benchmarking aggression identification in social media</article-title>
          ,
          <source>in: Proceedings of the First Workshop on Trolling, Aggression and Cyberbullying (TRAC-2018)</source>
          ,
          <article-title>Association for Computational Linguistics</article-title>
          , Santa Fe, New Mexico, USA,
          <year>2018</year>
          , pp.
          <fpage>1</fpage>
          -
          <lpage>11</lpage>
          . URL: https://aclanthology.org/W18-4401.
        </mixed-citation>
      </ref>
      <ref id="ref31">
        <mixed-citation>
          [31]
          <string-name>
            <given-names>Y.</given-names>
            <surname>Liu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Ott</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Goyal</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Du</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Joshi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Chen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>O.</given-names>
            <surname>Levy</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Lewis</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Zettlemoyer</surname>
          </string-name>
          ,
          <string-name>
            <given-names>V.</given-names>
            <surname>Stoyanov</surname>
          </string-name>
          ,
          <article-title>Roberta: A robustly optimized BERT pretraining approach</article-title>
          , CoRR abs/
          <year>1907</year>
          .11692 (
          <year>2019</year>
          ). URL: http://arxiv.org/abs/
          <year>1907</year>
          .11692. arXiv:
          <year>1907</year>
          .11692.
        </mixed-citation>
      </ref>
      <ref id="ref32">
        <mixed-citation>
          [32]
          <string-name>
            <given-names>A. P.</given-names>
            <surname>Dawid</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Skene</surname>
          </string-name>
          ,
          <article-title>Maximum likelihood estimation of observer error-rates using the em algorithm</article-title>
          ,
          <source>Journal of The Royal Statistical Society Series C-applied Statistics</source>
          <volume>28</volume>
          (
          <year>1979</year>
          )
          <fpage>20</fpage>
          -
          <lpage>28</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref33">
        <mixed-citation>
          [33]
          <string-name>
            <given-names>B.</given-names>
            <surname>Mathew</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Saha</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S. M.</given-names>
            <surname>Yimam</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Biemann</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Goyal</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Mukherjee</surname>
          </string-name>
          , Hatexplain: A
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>