arxiv.org web signal

Paper: Irrelevant Context Flips LLM Answers Despite Stable Scores

TL;DR

  • Prepending task-irrelevant context to benchmark questions causes little change in aggregate accuracy but shifts individual predictions in both directions.
  • Even pseudo-words made from randomly combining characters can markedly shift model predictions on a small fraction of examples.
  • The two-sided effect holds across a wide range of models and datasets, but which examples get flipped is largely model-specific.

A new paper on arXiv, The Illusion of Robustness, pokes at a comfortable assumption in language-model evaluation. If you prepend some task-irrelevant context to a benchmark question and the overall accuracy barely moves, the model looks stable. The authors argue that this aggregate stability 'masks significant per-example instability'. The headline score stays flat because flips in both directions cancel each other out.

The setup they describe is straightforward. Take benchmark questions, prepend task-irrelevant context, and compare what the model answers. Sometimes the extra text is semantically meaningless. The paper mentions pseudo-words formed by randomly combining characters, and even that is enough to 'markedly shift model predictions on a small fraction of examples.' Some examples get worse, others get better. The two-sided effect holds across a range of models and datasets, but which examples get flipped is 'largely model-specific'.

Why this matters for anyone shipping LLMs: aggregate accuracy is the metric almost every buyer uses to compare models, and it is exactly the metric the paper says can hide tail risk. If your production traffic looks like the 'context-rich settings' the paper flags, where user inputs come wrapped in long partially irrelevant context, two models with the same headline accuracy may be flipping on entirely different inputs. The authors argue this motivates 'per-example reliability evaluation of language models', which is a different kind of test than the leaderboard number.

The honest caveat is that the abstract does not name the specific models tested, the datasets used, or what fraction of examples actually flip, so the practical severity depends on details in the full paper. What the reporting also does not give you is a fix, whether prompt engineering, fine-tuning, or scale reliably damps this instability. The direction of travel it does point at is clear enough. Evaluation is drifting away from a single scalar and toward measuring stability input by input, which is closer to what enterprise buyers actually need as LLMs get dropped into workflows where task-irrelevant text is the norm rather than the exception.

Shared on Bluesky by 2 AI experts