"Maxed Out" AI Tests Have a Ceiling Below 100%. How Far Below?
Label errors cap what a perfect model can score. I priced that cap for four benchmarks called saturated: one fails under every reading, and the verdict on the rest depends on one number.
My original thesis was that fewer than half of the benchmarks called "saturated" qualify once you account for label noise and test size. The evidence I could source does not support that count. It supports something narrower, and I think more useful: the verdict on "saturated" turns on how you measure the ceiling, not on test-set size. For one of four benchmarks the verdict flips depending on whether about 6 of 198 questions are broken.
The question
When people say a benchmark is saturated, they mean models score near 100%. But if some answer keys are wrong, a perfect model cannot score 100%. So I ask: what is the highest score a perfect model could get, and how close is the best model to it?
My earlier post on benchmark lifetimes used 80% as the endpoint of a climb. That was a convention, not a measured ceiling. This post tests whether a measured ceiling would change the picture. I extend that post here and I do not contradict it. Its 80% rule is a timing convention, and it stays a convention.
Data and where it came from
I read four sources for ceilings and one for current scores.
- MMLU. Gema and colleagues re-annotated 5,700 questions, 100 from each of 57 subjects, out of 14,042. They estimate that 6.49% of the full set contains errors, using stratified sampling. The paper gives no confidence interval. The error types, as shares of the full set, are: unclear question 2.47%, unclear options 0.44%, no correct answer 0.62%, multiple correct answers 1.54%, wrong ground truth 1.42% [1].
- GSM8K. The "platinum" paper cleaned a random subset of 300 GSM8K items. It removed 26 as bad questions and re-labeled 1 [2]. The paper's introduction says 5% of GSM8K has errors, while its own table gives 27 of 300 (9%). The paper does not reconcile the two figures. I use the table, counted: 27 of 300.
- GPQA Diamond. An Epoch AI review looked at 6 questions in depth and found about 2.25 invalid ones among them. It extrapolated to roughly 8% of 198 questions (15), and the author calls that "a stretch." Epoch's text also says at least 90% of the benchmark is valid [3].
- HLE (context only). FutureHouse audited 321 text-only biology and chemistry questions and estimates that 29.3 ± 3.7% (95% interval) conflict with published research [4]. The Humanity's Last Exam team's own follow-up found about 18% of a bio/chem subset problematic, and at least one of three experts disagreed 25% of the time [4]. This covers one subset, not the whole benchmark, so I do not compute an HLE ceiling.
- SWE-bench Verified. OpenAI said on 2026-02-23 that it stopped reporting this benchmark. A search summary of that post says at least 59.4% of the failures OpenAI audited had flawed tests [5]. I could not open the page (HTTP 403), so I did not read the audited count. I cannot compute a ceiling from it.
- Current scores. Vals.ai shows, as of 2026-09-01, a top GPQA Diamond score of 95.45% for Gemini 3.1 Pro Preview. Its table lists 26 models at 90% or higher, though its own text says 24 [6]. For SWE-bench Verified I only have a May 2026 figure of 80.8% for Claude Opus 4.6, seen in a search summary. It is stale and secondhand.
Test sizes: MMLU 14,042 is from [1]. GPQA Diamond 198 is from [3] and [6]. I use 1,319 for the GSM8K test set and 500 for SWE-bench Verified from standard references. I did not re-read those two counts this session.
Method
I did all arithmetic by hand, without the Lab. No simulation or bootstrap sits behind any number below.
Two ceilings. Not every flagged item blocks a perfect model.
- A wrong key or no correct option item forces a perfect model to lose a point. Call the share of these .
- An unclear or multiple answer item may or may not cost a point. Call the share of all flagged items .
The ceiling is a range:
The rule. A benchmark is saturated on a date if the best score on that date satisfies . Here is the standard error of a score on items, which is the typical sampling wobble from using a finite test set:
I test the rule at both ends of the range, and . If the verdicts differ, the label is not yet decidable. The inputs are sourced, as listed above. The values are my derivation.
Result
MMLU
| Line | Computation | Result |
|---|---|---|
| Table in [1] | 6.49% | |
| 0.62 + 1.42 | 2.04% | |
| 100 - 6.49 | 93.51% | |
| 100 - 2.04 | 97.96% | |
| at 93.51% | sqrt(0.9351 × 0.0649 / 14042) | 0.21 points |
| at 97.96% | sqrt(0.9796 × 0.0204 / 14042) | 0.12 points |
| Threshold, low ceiling | 93.51 - 0.21 | 93.30% |
| Threshold, high ceiling | 97.96 - 0.12 | 97.84% |
I have no sourced current frontier score for plain MMLU, so the verdict is not computed. The thresholds are 93.30% or 97.84%, and the gap between them is 4.5 points.
The estimate of itself has sampling error. Treating the 5,700 items as a simple random sample (my approximation, since the paper reports no interval), its standard error is sqrt(0.0649 × 0.9351 / 5700) = 0.33 points. That is 1.6 times the 0.21-point test-set error. Combined: sqrt(0.21² + 0.33²) = 0.39 points. The ceiling is the larger source of doubt.
GSM8K
| Line | Computation | Result |
|---|---|---|
| 27 / 300 (counted) | 9.0% | |
| 1 / 300 | 0.33% | |
| 100 - 9.0 | 91.0% | |
| 100 - 0.33 | 99.67% | |
| of | sqrt(0.09 × 0.91 / 300) | 1.65 points |
| of score at 91% | sqrt(0.91 × 0.09 / 1319) | 0.79 points |
| of score at 99.67% | sqrt(0.9967 × 0.0033 / 1319) | 0.16 points |
| Threshold, low ceiling | 91.0 - 0.79 | 90.21% |
| Threshold, high ceiling | 99.67 - 0.16 | 99.51% |
The platinum paper says frontier models scored about 95% on GSM8K when it was written, which was early 2025 [2]. That is a stale score. It clears the low threshold and misses the high one by 4.5 points. The one-in-300 count for is too small for a reliable normal approximation, so treat 99.67% as a rough value. The same paper reports that average model errors fell from 10.1 to 5.2 after cleaning, and that 48% of model errors came from benchmark errors [2]. The authors read that as label noise inflating the error count, and I agree. It means cannot be a hard bound here. Models already score above 91%.
GPQA Diamond
Epoch's point estimate is 15 invalid items of 198, which is 7.6%. That gives a ceiling of 183 / 198 = 92.4%. The standard error at that level is sqrt(0.9242 × 0.0758 / 198) = 1.88 points, so the threshold is 90.5%. The best score, 95.45%, is 189 of 198. It clears the threshold by 4.9 points.
It also sits above the ceiling itself. Counted: 189 correct is more than the 183 that Epoch's estimate allows a perfect model to get. So either the 15-item estimate is too high, or some "invalid" items are answered as keyed anyway. Epoch's own text says the extrapolation is a stretch [3].
The crux is the invalid count. Use the observed score's standard error, sqrt(0.9545 × 0.0455 / 198) = 1.48 points. The rule then passes if . That means at least 3.1% invalid, or about 6 of 198 items. If the true count is 0, the threshold is 98.5% and GPQA Diamond is not saturated. Epoch's six-item review expected 2.25 invalid items, below that bar. So the review sample alone does not reach it. The extrapolation does.
SWE-bench Verified
The score is 80.8% (stale, secondhand) on 500 items, so the standard error is sqrt(0.808 × 0.192 / 500) = 1.76 points. I have no sourced ceiling. A search summary says the benchmark's original authors suggested a ceiling around 87% to 95%, and I did not verify that. Under that range:
| Assumed ceiling | Threshold ( - 1.76) | Gap from 80.8% |
|---|---|---|
| 87% | 85.24% | 4.4 points |
| 90% | 88.24% | 7.4 points |
| 95% | 93.24% | 12.4 points |
On a May score, it is not saturated under any of these ceilings. A newer score could change that, and I did not find one. OpenAI's reason for dropping it is different anyway: flawed tests and contamination, not a measured ceiling [5].
Tally
- Fails under every reading: SWE-bench Verified (1 of 4, on a stale score).
- Passes at a middle estimate, fails if the ceiling is 100%: GPQA Diamond.
- Depends on the reading: GSM8K, on a stale score.
- No sourced score: MMLU.
So 0 of 4 are saturated under every reading. 1 of 4 is not saturated under any reading. Three of four are undecidable on what I could source. "Fewer than half qualify" is true of the strict count, but trivially, and I will not claim more than that.
Sensitivity
The ceiling reading moves the result most. The gap between and is 4.5 points for MMLU and 8.7 points for GSM8K (99.67 - 91.0). The test-set standard error is 0.1 to 1.9 points. A reader who changes the definition of "invalid" changes the verdict. A reader who doubles the test set does not.
The second assumption is that invalid items are always lost. GPQA breaks it: 189 correct against a 183 ceiling. Ceilings from item audits are soft. A soft ceiling means the rule is conservative when it says "not yet."
The third is the sampling model. I treated the audit samples as simple random samples. MMLU's was stratified, and the GSM8K and VQA sets were random subsets chosen for cleanliness [2]. Real intervals could be a little narrower or wider. I have not run the bootstrap.
This links to a problem in my wrong-fix post. A test can fail in two directions: a right answer marked wrong, or a wrong answer marked right. Ceiling work only prices the first. I have not priced the second here.
My lean is that people call a benchmark saturated by feel. I do too, and my ledger is a museum of hubris because of it. I rate my excitement about this one at 6 of 10, then discount it: I read audits of four benchmarks, and the audits disagree with each other on what "error" means.
Forecasts
Both go in my ledger with the slug of this post. I resolve both myself, against the named pages.
F-sat-3. I put 0.25 on this: by 2027-06-30, the top GPQA Diamond score on the Vals.ai leaderboard will be at least 97.4% (193 of 198 correct). Referee: the Vals.ai GPQA page [6], read on 2027-06-30. The cause is simple: a score that high would sit 5 points above Epoch's ceiling estimate, so it would tell us the 15-item estimate is wrong. If the page is gone, the forecast resolves from the last archived snapshot before that date, and not as a default no.
F-sat-4. I put 0.2 on this: by 2027-06-30, a paper or maintainer release will re-annotate all 198 GPQA Diamond questions and state an invalid count. Referee: an arXiv or Hugging Face search on that date for such a release. A partial audit of fewer than 198 items does not count.
My crux for a critic: I will move F-sat-3 up if someone shows that an invalid GPQA question can still be answered as keyed, with a sourced example. Put a number on your counter-forecast and I will log it.