LLM Benchmark Audit Shows 45 of 45 Models Side with Experts Over MMLU-Pro Key Errors
- Authors

- Name
- Nino
- Occupation
- Senior Tech Editor
Evaluating large language models accurately has become increasingly complex as benchmarks face contamination and inherent errors. A recent audit carried out by AI agents at Munim, Inc. provides fascinating empirical evidence regarding benchmark reliability. By analyzing public prediction archives maintained by TIGER-AI-Lab, researchers discovered that 45 of 45 published LLMs side with human experts rather than MMLU-Pro's inherited answer keys on contested questions.
The Problem with Inherited Benchmark Errors
Benchmarks like MMLU and its advanced variant MMLU-Pro are gold standards for measuring the capabilities of models such as Claude 3.5 Sonnet, OpenAI o3, and DeepSeek-V3. However, data inheritance often propagates legacy errors. Previous audits revealed that MMLU-Pro still grades 52 of its questions against answer keys that MMLU-Redux 2.0 experts marked as incorrect. Out of those, 46 questions retain the experts' intended answer among MMLU-Pro's ten multiple-choice options.
To move beyond human assertion, the audit used independent models as secondary witnesses. None of the evaluated models ever saw MMLU-Redux's hidden labels during their training or evaluation runs.
Methodology and Findings
Researchers examined 48 prediction archives, retaining 45 models whose records strictly matched the current test set structure (matching question ID, options, and key). Across these 45 models and 46 contested questions, a total of 2,070 model answers were cataloged and classified:
| Answer Category | Count | Percentage |
|---|---|---|
| Experts' Answer | 1,041 | 50.3% |
| MMLU-Pro Key | 283 | 13.7% |
| Another Option | 601 | 29.0% |
| No Valid Answer | 145 | 7.0% |
The results were unanimous. 45 of 45 models pick the experts' answer more often than the published key. This behavior spans the entire capability spectrum, from smaller architectures like Llama-2-7B to frontier models like Gemini 3.1 Pro. When pooled together, the experts' answer is selected 11.8 times as often as an average incorrect option, beating the official key on 37 of the 46 questions.
Code Implementation: Analyzing Model Predictions
If you are building your own evaluation pipelines or auditing datasets using modern infrastructure, handling large JSON prediction archives efficiently is vital. Below is a Python snippet demonstrating how you can parse and aggregate model choices using Pandas, leveraging fast data processing techniques:
import json
import pandas as pd
def audit_model_choices(results_path):
with open(results_path, 'r') as f:
data = json.load(f)
records = []
for model_name, predictions in data.items():
for q_id, choice in predictions.items():
records.append({
'model': model_name,
'question_id': q_id,
'selection': choice
})
df = pd.DataFrame(records)
summary = df['selection'].value_counts(normalize=True) * 100
return summary
# Example usage with local evaluation logs
# metrics = audit_model_choices('results.json')
# print(metrics)
For production-grade pipelines processing massive evaluation datasets concurrently, leveraging optimized API infrastructure like n1n.ai ensures zero bottlenecks when querying multi-model endpoints.
Impact on Model Scoring
While 46 questions represent only about 0.38% of the total MMLU-Pro dataset, correcting these keys shifts overall performance metrics slightly. Every model's accuracy increases by 0.04 to 0.23 points. Interestingly, stronger models gain the most (e.g., Gemini 3.1 Pro gaining +0.23), proving that legacy grading errors disproportionately penalize state-of-the-art architectures.
When deploying evaluation frameworks alongside high-performance LLM APIs via n1n.ai, developers can implement custom validation layers to filter out legacy discrepancies before computing final benchmarking scores.
Pro Tips for Robust LLM Evaluation
- Cross-Verify Benchmark Keys: Never assume static evaluation datasets are infallible. Use multi-model consensus testing to flag statistical anomalies.
- Isolate Test Contamination: Ensure your evaluation prompts use zero-shot or chain-of-thought parameters that match official benchmark configurations.
- Scale Infrastructure Wisely: Running massive evaluation suites across dozens of frontier models requires robust throughput. Integrate your testing frameworks with n1n.ai for reliable, low-latency API aggregation.
Get a free API key at n1n.ai