How We Define Harm Impacts Data Annotations: Explaining How Annotators Distinguish Hateful, Offensive, and Toxic Comments
On the map: LLM safety and security → Safety alignment, refusal and guardrails
Abstract (arXiv)
Computational social science research has made advances in machine learning and natural language processing that support content moderators in detecting harmful content. These advances often rely on training datasets annotated by crowdworkers for harmful content. In designing instructions for annotation tasks to generate training data for these algorithms, researchers often treat the harm concepts that we train algorithms to detect - 'hateful', 'offensive', 'toxic', 'racist', 'sexist', etc. - as interchangeable. In this work, we studied whether the way that researchers define 'harm' affects annotation outcomes. Using Venn diagrams, information gain comparisons, and content analyses, we reveal that annotators do not use the concepts 'hateful', 'offensive', and 'toxic' interchangeably. We identify that features of harm definitions and annotators' individual characteristics explain much of how annotators use these terms differently. Our results offer empirical evidence discouraging the common practice of using harm concepts interchangeably in content moderation research. Instead, researchers should make specific choices about which harm concepts to analyze based on their research goals. Recognizing that researchers are often resource constrained, we also encourage researchers to provide information to bound their findings when their concepts of interest differ from concepts that off-the-shelf harmful content detection algorithms identify. Finally, we encourage algorithm providers to ensure their instruments can adapt to contextually-specific content detection goals (e.g., soliciting instrument users' feedback).
Key facts. Cited by 2 papers in the map (data through 14 Oct 2026). Placed in Safety alignment, refusal and guardrails, one of 12 directions in LLM safety and security. Builds on 10 of its 39 references that are in the map. First posted on arXiv 12 Sep 2023.
Builds on
10 of 39 references.
References · 10
- 2017Automated Hate Speech Detection and the Problem of Offensive Languagecited by 736
- 2017Understanding Abuse: A Typology of Abusive Language Detection Subtaskscited by 116
- 2018Hate Lingo: A Target-based Linguistic Analysis of Hate Speech in Social Mediacited by 59
- 2021Cross-replication Reliability -- An Empirical Approach to Interpreting Inter-rater Reliabilitycited by 31
- 2018Peer to Peer Hate: Hate Speech Instigators and Their Targetscited by 30
- 2022KOLD: Korean Offensive Language Datasetcited by 14
- 2021Principled Evaluation with Human Labels: One Rater at a Time and Rater Equivalencecited by 7
- 2021Predicting Different Types of Subtle Toxicity in Unhealthy Online Conversationscited by 5
- 2019Conversational Networks for Automatic Online Moderationcited by 3
- 2017Impact Of Content Features For Automatic Online Abuse Detectioncited by 1
Built on by
Citing papers per year: 2026: 2.
2 papers.
Similar, not cited
Close in wording, no citation either way
- 2022Handling and Presenting Harmful Text in NLP Research
- 2024Harmful YouTube Video Detection: A Taxonomy of Online Harm and MLLMs as Alternative Annotators
- 2023"HOT" ChatGPT: The promise of ChatGPT in detecting and discriminating hateful, offensive, and toxic comments on social media
- 2025Something Just Like TRuST : Toxicity Recognition of Span and Target
- 2026Decomposing and Predicting Annotation Disagreement in Harmful Content Across Languages
- 2024Analyzing Toxicity in Deep Conversations: A Reddit Case Study
- 2025How AI Fails: An Interactive Pedagogical Tool for Demonstrating Dialectal Bias in Automated Toxicity Models
- 2025Towards Safer Pretraining: Analyzing and Filtering Harmful Content in Webscale datasets for Responsible LLMs