SYNTOLOGY HomeExplorerAtlasCodeMethodologyAboutDevelopersFeedPricing
Paper · 2402.01781 · ACL · 2024

When Benchmarks are Targets: Revealing the Sensitivity of Large Language Model Leaderboards

Haidar Khan, Saiful Bari, Norah Alzahrani, Yazeed Alnumay, Shaykhah Alsubaie, Abdullah Alyahya, Yousef Almushayqih, Abdulrahman Faisal, Nouf Mirza, Nora Alotaibi, Areeb Al-Twairesh, Alowisheq, and 6 more

arXiv · PDF · Open in the Atlas

Code that ran

2 of 2 samples (functions and classes) lifted from this paper's linked repositories executed on a synthesized input in Syntology's jail (0 of them constructed an object rather than computing a result; 1 honoured the contract we drafted, 0 violated it and 0 have no contract verdict; 1 failure of our instrument; 0 no recorded run), measured 2026-11-22; repository links from the Papers with Code archive attributed under CC BY-SA, no affiliation; bodies inline only under a permissive licence as GitHub detects it. Not a reproduction of the paper's results.

"Ran" means the function executed on a synthesized input and returned a value. It is not a reproduction of the paper's results. This record, dated, as JSON: /api/ran/2402.01781.json · badge: /api/ran/2402.01781.svg

Each repository's role is a label: a classifier's output recorded on the link, or, where no role is recorded, what the Papers with Code archive marked. The line under it names its basis. Neither says who wrote the code.

RepositoryRoleRan
national-center-for-ai-saudi-arabia/lm-evaluation-harness extension (classifier label)
classifier basis: classifier_2025
2 ran · 0 no recorded run
FunctionStatusWhere it lives
calculate_z_value Ran
ran, honoured the contract we drafted
national-center-for-ai-saudi-arabia/lm-evaluation-harness/scripts/model_comparator.py
code served (permissive licence) · get_code("25c98717dbac36c9")
How it ran

Ran in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API) and returned tuple, ndim 1, dtype family float; no output shape is stated. The image it ran in was not recorded. If your copy returns the same type and ndim on these inputs, it matched what we observed; nothing here checks that. It does NOT mean the output is correct: nothing has compared it to the paper.

import numpy as np
import scipy.stats

# Construct two result dictionaries with the required keys
res1 = {
    'acc,none': 0.85,
    'acc_stderr,none': 0.02
}

res2 = {
    'acc,none': 0.78,
    'acc_stderr,none': 0.025
}

ARGS = {
    'res1': res1,
    'res2': res2
}
Setup block drafted by
a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API
Imports
numpy, scipy — import names as written, not package names to install; a name the repository itself provides is not a package
Returned
type tuple, ndim 1, dtype family float — a tuple output has no array shape of its own; none is stated
dtype family
int means an integer dtype; float means any other dtype the instrument saw, bool and complex included (fixture_check.py records only these two families)
Environment
image not recorded; re-verify against syntology-harvest-sandbox:v5-deps; not recorded for this sample: the harness installs a cuda-to-cpu shim (cuda_shim.py) before every sample and no run records whether a sample needed it; seed: none by the harness; any seed is in the setup block
print_results Ran
ran; our contract draft was wrong, not the code
national-center-for-ai-saudi-arabia/lm-evaluation-harness/scripts/model_comparator.py
code served (permissive licence) · get_code("4cf4873400b2f793")
How it ran

Ran in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API) and returned DataFrame. The image it ran in was not recorded. If your copy returns the same type on these inputs, it matched what we observed; nothing here checks that. It does NOT mean the output is correct: nothing has compared it to the paper.

import torch
import numpy as np
import pandas as pd
from typing import Dict, List

torch.manual_seed(0)

# Construct data_to_print: list of 2 dicts with task results
model1_data = {
    'task_a': {
        'acc,none': 0.85,
        'acc_stderr,none': 0.02
    },
    'task_b': {
        'acc,none': 0.92,
        'acc_stderr,none': 0.015
    }
}

model2_data = {
    'task_a': {
        'acc,none': 0.87,
        'acc_stderr,none': 0.021
    },
    'task_b': {
        'acc,none': 0.90,
        'acc_stderr,none': 0.018
    }
}

data_to_print = [model1_data, model2_data]

# Construct results_dict with z-scores and p-values for each task
results_dict = {
    'task_a': {
        'z': 0.45,
        'p_value': 0.65
    },
    'task_b': {
        'z': -1.2,
        'p_value': 0.23
    }
}

# Construct alpha threshold
alpha = 0.05

ARGS = {
    'data_to_print': data_to_print,
    'results_dict': results_dict,
    'alpha': alpha
}
Setup block drafted by
a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API
Imports
numpy, pandas, torch — import names as written, not package names to install; a name the repository itself provides is not a package
Returned
type DataFrame — a DataFrame output has no array shape of its own; none is stated — the instrument coerces any output to an array; for a DataFrame output the recorded ndim 2 and dtype family float describe that coercion, not the output, and are not stated
Environment
image not recorded; re-verify against syntology-harvest-sandbox:v5-deps; not recorded for this sample: the harness installs a cuda-to-cpu shim (cuda_shim.py) before every sample and no run records whether a sample needed it; seed: none by the harness; any seed is in the setup block

Also present in other papers' code

Of 2 samples lifted from this paper's linked repositories, 2 carry a function identity and 0 do not. Of the 2 distinct functions with an identity, 0 are also present in other papers whose code we hold (0 with at least one paper dated earlier, 0 the same month, 0 later) and 2 are only here among the 52,977 papers whose code Syntology holds (as of 2026-09-26).

Only here means: among the 52,977 papers whose code Syntology holds (51,887 with lifted samples, 1,090 through their assemblies only), as of 2026-09-26, no other paper's lifted samples or current assembly bricks contain an identical function body after normalisation.

Presence, not direction: an identical function body in two papers' repositories does not say who wrote it, which came from which, or that either paper's method rests on it. Matching is exact after normalisation, so a renamed or edited function is not matched. Dates are when papers appeared, not when code was written. Only .py files the harvester lifted are covered; notebooks are not read. A new-style arXiv id YYMM.NNNN dates a paper to the month 20YY-MM; otherwise Paper.year dates it to the year; otherwise it is undated. Dates are when the paper appeared, not when the code was written. Read 2026-11-22.

Repositories linked to this paper

Some links come from the archived Papers with Code dataset (CC BY-SA 4.0): attribution and licence.

Abstract

Large Language Model (LLM) leaderboards based on benchmark rankings are regularly used to guide practitioners in model selection. Often, the published leaderboard rankings are taken at face value -we show this is a (potentially costly) mistake. Under existing leaderboards, the relative performance of LLMs is highly sensitive to (often minute) details. We show that for popular multiple-choice question benchmarks (e.g., MMLU), minor perturbations to the benchmark, such as changing the order of choices or the method of answer selection, result in changes in rankings up to 8 positions. We explain this phenomenon by conducting systematic experiments over three broad categories of benchmark perturbations and identifying the sources of this behavior. Our analysis results in several best-practice recommendations, including the advantage of a hybrid scoring method for answer selection. Our study highlights the dangers of relying on simple benchmark evaluations and charts the path for more robust evaluation schemes on the existing benchmarks.

For agents

The same record, over MCP at https://syntology.ai/mcp:

get_harvested_code_for_paper("2402.01781")
get_code_for_paper("2402.01781")
have("2402.01781")

The run record, dated, one paper per request, free:

curl https://syntology.ai/api/ran/2402.01781.json

A badge for a README (the split and the date, never a ratio):

[![Syntology run record](https://syntology.ai/api/ran/2402.01781.svg)](https://syntology.ai/paper/2402.01781)

Connect an agent — have() is free.