Skip to content
Modelwire
Subscribe

LLM judges produce inconsistent scores across model versions

Source published ·Modelwire updated

Original coverage: arXiv cs.CL ↗·How Modelwire adds context

Illustration accompanying: When the Judge Changes, So Does the Measurement: Auditing LLM-as-Judge Reliability

The development

A new arXiv study exposes a critical reliability gap in LLM-based evaluation systems: swapping judges produces inconsistent scores even when candidate responses remain identical. Researchers tested two practical upgrade paths (Qwen3 scaling and MiniMax API releases) across four judgment datasets, finding that judge improvements are not interchangeable. Only Qwen3's 1.7B-to-4B transition yielded robust gains, while MiniMax adjacent versions diverged significantly. Stronger judges partially mitigate position and verbosity bias but cannot eliminate it. The work signals that production systems relying on LLM judges for quality control face hidden measurement drift, undermining reproducibility and trust in automated evaluation pipelines.

Modelwire’s AI-generated summary of coverage from arXiv cs.CL.

Modelwire analysis

Explainer

Our AI-generated reading of the wider context and the next developments to watch.

The study's most underreported finding is directional: judge upgrades don't simply raise all scores uniformly, they shift relative rankings between candidate responses, meaning a system that passed quality control under one judge may fail under its successor even if the underlying model being evaluated hasn't changed at all.

This connects most directly to the model merging paper covered the same day ('Improving Ad-hoc Search Effectiveness for Conversational Information Retrieval via Model Merging'), which also grapples with the instability introduced when swapping or adapting components in evaluation-adjacent pipelines. Both papers are really asking the same question from different angles: how do you maintain consistent measurement when the measuring instrument itself is subject to change? More broadly, the reproducibility concern here sits alongside the ImputeViz coverage from July 9th, which flagged missing-data handling as a hidden bias source in scientific pipelines. The pattern across these papers is a growing research focus on making ML infrastructure auditable, not just performant.

Watch whether benchmark suites like LMSYS Chatbot Arena or AlpacaEval publish explicit judge-versioning policies within the next two quarters. If they do, this paper will have had measurable influence on evaluation standards; if not, the measurement drift problem remains unaddressed in the venues that shape model rankings.

This interpretation is generated from the summary above and available source metadata. Our methodology · Report an error

MentionsQwen3 · MiniMax · arXiv

MW

How this coverage is produced

Modelwire uses AI to generate summaries and context from source headlines, snippets, and selected archive coverage. Automated checks do not verify every claim, and items are not routinely reviewed by a person before publication. Zacaria Solis operates the site. Read the linked source for the full evidence and report errors through our corrections process.

Modelwire summarizes, we don’t republish. arXiv cs.CL originally reported this story as “When the Judge Changes, So Does the Measurement: Auditing LLM-as-Judge Reliability”. The full content lives on arxiv.org. If you’re a publisher and want a different summarization policy for your work, see our takedown page.

LLM judges produce inconsistent scores across model versions · Modelwire