← Latest papers
💬 NLP

Challenger at MultiPRIDE: Is It Hate Speech or Reclaimed?

This paper presents a computationally efficient and interpretable approach for the MultiPride Shared Task that distinguishes hate speech from reclaimed language by combining dense semantic embeddings, Cleanlab-based label-noise filtering, and an MLP classifier to achieve robust performance despite extreme class imbalance.

Original authors: Hadi Bayrami Asl Tekanlou, Mahdi Bakhtiyarzadeh, Jafar Razmara

Published 2026-06-02
📖 5 min read🧠 Deep dive

Original authors: Hadi Bayrami Asl Tekanlou, Mahdi Bakhtiyarzadeh, Jafar Razmara

Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer

Imagine the internet as a giant, noisy town square. In this square, people sometimes shout things that are meant to hurt others—this is hate speech. But there's a twist: sometimes, the people being targeted take those same hurtful words, grab them back, and use them among themselves to show they are strong and united. This is called reclaimed language.

Think of it like a family nickname. If a stranger calls your family a silly name, it's an insult. But if your family uses that same silly name to laugh together, it's a sign of love. The problem for computers is that they are terrible at understanding the difference between a stranger shouting an insult and a family member using a nickname. They often get confused and think the family is being mean, too.

This paper describes a team from the University of Tabriz who built a "smart detective" to solve this specific confusion for a competition called MultiPRIDE. Here is how they did it, broken down into simple steps:

1. The Problem: The "False Alarm"

The team noticed that computers often make "false alarms." They see a word that is usually bad (like a slur) and immediately flag it as hate speech, even if it's being used by the LGBTQ+ community to support each other. This stops people from expressing themselves freely. The goal was to teach the computer to tell the difference between a "bad guy" using a slur and a "good guy" reclaiming it.

2. The Solution: A Three-Step Cleaning Process

The team built a system that acts like a high-tech filter. Instead of just reading words, they used a three-step process:

  • Step 1: The Janitor (Data Cleaning & Augmentation)
    First, they cleaned the messy text. They swept away URLs, user names, and emojis (which can confuse the computer) but kept the hashtags because they hold important meaning.

    • The Analogy: Imagine you are trying to study a messy room. You throw away the trash (URLs) but keep the books (hashtags) because they tell the story.
    • The Twist: They also noticed they didn't have enough examples of the "reclaimed" language (the minority class). So, they used a "translation machine" (Google Translate) to translate these rare examples into other languages (like French or German) and then back to English. This created new, fake examples to help the computer learn better, like making extra copies of a rare recipe so the chef can practice more.
  • Step 2: The Translator (Embeddings)
    They used a powerful tool called intfloat/e5-large-v2 to turn sentences into "dense maps."

    • The Analogy: Instead of just looking at the words "I love you," the computer converts the whole sentence into a complex set of coordinates on a map. This map captures the feeling and context of the sentence, not just the dictionary definition. It helps the computer understand that "I love you" said by a parent feels different than "I love you" said by a stranger in a creepy way.
  • Step 3: The Quality Control (Label Cleaning)
    Sometimes, the data itself has mistakes (bad labels). The team used a tool called Cleanlab to act as a quality inspector.

    • The Analogy: Imagine a teacher grading a test. If the teacher thinks a student's answer is wrong but the answer key says it's right, the teacher double-checks. If the teacher is sure the answer key is wrong, they throw that specific question out of the test so it doesn't confuse the students later. This step removed "noisy" or confusing examples from the training data.

3. The Final Brain (The Classifier)

After all that cleaning and translating, they fed the data into a simple but effective "brain" called a Multi-layer Perceptron (MLP).

  • The Analogy: Think of this as a lightweight, fast-running robot. It doesn't need a supercomputer to think; it just needs the clean, high-quality maps from Step 2 to make a quick decision: "Is this hate speech, or is this reclaimed language?"

4. The Results: How Did They Do?

The team tested their system on tweets in English, Italian, and Spanish.

  • The Good News: Their system was very good at spotting the "clean" hate speech (Label 0). It was like a perfect detective for obvious insults.
  • The Challenge: It struggled a bit more with the "reclaimed" language (Label 1), especially in English. This is because there were far fewer examples of reclaimed language in the data to begin with (a problem called "class imbalance").
  • The Verdict: Even with this imbalance, their system performed well overall. They showed that you don't need a massive, expensive supercomputer to solve this; a smart, lightweight system with good cleaning steps can do a great job.

Summary

The paper argues that to stop computers from mislabeling friendly reclaimed language as hate, we need to:

  1. Clean the data carefully.
  2. Use smart translations to create more examples of the rare cases.
  3. Double-check the data for mistakes.
  4. Use a simple, fast model to make the final call.

They proved that this "lightweight" approach works well across different languages, offering a practical way to handle the tricky nuance of online speech without needing huge amounts of computing power.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →