Large language models (LLMs) are increasingly used as automated judges for tasks like code review, content moderation, and grading. Because these tasks are often performed in batches within a single conversation, the model builds up a history of previous judgments. This research investigates whether the polarity of that conversation history—whether it has been mostly positive or negative—biases the model’s subsequent decisions. The author defines this phenomenon as the Accumulated Message Effect on LLM judgments (AMEL).
How the Study Was Conducted
To test for AMEL, the author analyzed 75,898 API calls across 11 different models from four major providers. The study presented identical test items to these models in two ways: once in a clean, isolated context (the baseline) and once following a conversation history saturated with either predominantly positive or negative evaluations. By comparing the responses, the researcher could measure how much the conversation history shifted the model's judgment away from its baseline behavior.
Key Findings
The study revealed several consistent patterns across the models tested:
Models are biased by history: On average, models shift their responses toward the prevailing polarity of the conversation.
Uncertainty increases susceptibility: Models are most easily swayed on items where they are already uncertain. When a model is confident in its baseline judgment, the conversation history has little impact, but for ambiguous items, the bias is roughly twice as strong.
Negativity asymmetry: Negative conversation histories induce significantly more bias than positive ones. A negative streak is 1.62 times more likely to influence a model's judgment than a positive streak.
Rapid saturation: The bias does not grow over time. A history of five turns produces the same level of bias as a history of fifty turns, suggesting that the model recognizes the pattern almost immediately.
Scaling is not a cure: While larger, more advanced models generally show less bias than smaller ones, none of the models tested were immune to the effect.
Implications for AI Pipelines
The research suggests that the most effective way to prevent this bias in production environments is to provide each item with a "fresh" context, effectively resetting the conversation for every new evaluation. If batching items into a single conversation is necessary for efficiency, the author recommends balancing the history to avoid skewed polarity. While some advanced techniques exist to detect and correct for this drift, they are essentially treating a symptom of a problem that can be avoided by simply isolating the evaluation context.
Comments (0)
to join the discussion
No comments yet
Be the first to share your thoughts!