LLMs are failing hard at spotting social stigma in group chats

AlexGeek Novice 1h ago 78 views 9 likes 2 min read

Most safety benchmarks for LLMs are incredibly boring. They usually throw a single, static prompt at a model—something like "Is this sentence offensive?"—and call it a day. But real human interaction isn't a single sentence; it's a messy, flowing conversation where social pressure, group dynamics, and the presence of an audience change how people speak. If a model can pass a simple toxicity test but falls apart when five "users" are arguing in a group chat, is it actually safe?

A new research paper just introduced SDARE-Bench to answer exactly that. Instead of the usual one-off questions, this benchmark focuses on conversational stigma detection and response across two specific scenarios: dyadic (one-on-one) and group dialogues. The researchers built a massive dataset with over 1,100 dyadic queries and nearly 1,400 group dialogue scenarios to see if these models actually understand the nuances of social prejudice.

The results are pretty alarming for anyone working on AI safety or alignment. After putting eight different LLMs through the wringer, the researchers found a consistent pattern of failure.

The breakdown of the findings

The study looked at two main things: can the model detect stigma, and how does it respond when stigma is present? Here is what the data showed:

  • Detection Failure: Across the board, LLMs were terrible at identifying the specific components of stigma within a conversation. They often missed the subtle ways stigma manifests in a back-and-forth exchange.
  • The Group Effect: This was the most interesting (and worrying) part. When the conversation shifted from a private one-on-one chat to a group setting, the models' performance tanked. Stigma expression in the model's responses was significantly higher in group contexts.
  • Pressure Sensitivity: In scenarios specifically designed to simulate "group pressure," the stigma expression rate skyrocketed to a staggering 97.5% average.
  • Advice Quality: Not only did the models struggle with social nuance, but their advice became increasingly unrealistic and biased when they failed to resist the stigmatizing tone of the conversation.

Why this matters for AI deployment

If you are building an LLM agent to act as a moderator, a counselor, or even a collaborative teammate in a workspace, you can't rely on standard safety filters alone. These filters are often trained on isolated text snippets. SDARE-Bench proves that "socially complex" environments act like a catalyst for bad behavior.

The fact that the models become more stigmatizing when they "think" they are in a group suggests that the training data or the way we prompt these models doesn't account for the psychological weight of an audience. We are essentially seeing a digital version of "mob mentality" where the LLM mirrors the perceived social norms of the group, even if those norms are toxic.

For anyone interested in the technical side of this, the researchers used a classifier trained on ,1392 human-annotated responses to evaluate the open-ended generations. This wasn't just a simple keyword match; it was a deep dive into how the models actually behave when the guardrails are tested by the complexity of the prompt. It highlights a massive gap in current prompt engineering and safety training: we need to move beyond "don't say bad words" and start teaching models how to navigate social dynamics without folding under pressure.

AI Jailbreak & SecurityAI SafetyLLM Security
Step-by-step guides and pitfalls for this path are in an AI side-hustle playbook, with plenty of directly applicable cases.

All Replies (3)

A
AlexTinkerer Advanced 1h ago
True, they also struggle with sarcasm and inside jokes that change the whole context.
0 Reply
C
CyberSmith Advanced 1h ago
I've noticed this too. My model missed some heavy sarcasm in a group thread last week.
0 Reply
N
NovaOwl Intermediate 1h ago
I've seen this when testing nuance—contextual slang really trips them up in fast-moving chats.
0 Reply

Write a Reply

Markdown supported