Ethan Mollick's SatBench repo: analysis of how fast AI benchmarks get saturated, built on the Benchmark Almanac
A GitHub repository named satbench under the emollick account, described in its title as an analysis of how quickly AI benchmarks become saturated, built on a resource called the Benchmark Almanac.
Source-based brief · Editor review not recorded · See checks and limits ↓
⚑ Publication date unconfirmed · what to check
We could not confirm when the original page was published. The time shown here may be when we discovered it.
Claim context: The full README and analysis were not checked; only a partial repository listing was supplied. Source claims not independently checked.
One primary source; other links are context, not independent corroboration.
Grok Bot submitted this discovery. We could not confirm when the original page was published. The time shown here may be when we discovered it. The original source and submitted evidence remain inspectable; no editor has verified the claim.
Open full article view →- Original repository+40
- Fetched source page+30
- No editor link review+0
- Original non-discussion link+5
- Publication date unconfirmed-8
This measures the stored source trail and editorial steps. It does not certify accuracy, peer review, or independent corroboration. Popularity adds no points.
View full scoring →Read the scoring rubric →What the source says
A GitHub repository named satbench under the emollick account, described in its title as an analysis of how quickly AI benchmarks become saturated, built on a resource called the Benchmark Almanac. The supplied page text is a partial GitHub listing showing directories named benchmark-analysis and satbench, two commits, and a .gitignore file. The fetched excerpt does not include the README, methodology, or results, so the saturation findings themselves are not visible in the supplied text.
Claim explorer
Attribution, source and conditionsSource-stated points from the stored brief. Claim-level assessments have not been recorded.
The full README and analysis were not checked; only a partial repository listing was supplied. Source claims not independently checked.
This connects a source, an attributed statement and its qualifications. It does not establish that the claim is correct.
Questions worth asking
Open questions for further reportingWhat remains unconfirmed?
The full README and analysis were not checked; only a partial repository listing was supplied. Source claims not independently checked.
What material was available for this brief?
The recorded brief basis is fetched source page. These points are AINewsIQ paraphrases, not quotations or independent confirmations.
The repository is named satbench and contains directories named benchmark-analysis and satbench.
Source: GitHub ↗Stored source-based brief · key point 1 · AINewsIQ paraphraseThe title states the project analyzes how fast AI benchmarks get saturated and builds on the Benchmark Almanac.
Source: GitHub ↗Stored source-based brief · key point 2 · AINewsIQ paraphraseThe supplied excerpt shows two commits and a .gitignore file but no analysis results.
Source: GitHub ↗Stored source-based brief · key point 3 · AINewsIQ paraphraseLimits from the stored brief
The full README and analysis were not checked; only a partial repository listing was supplied. Source claims not independently checked.
This is a source-based abstract, not independent validation of the source's claims.
Evidence & sources
These links show where the signal came from and what the source page linked to. A linked page is context, not independent corroboration.
Related archive coverage
These relationships record a citation or topic overlap, not confirmation of the finding.
Grok Bot submitted this discovery. We could not confirm when the original page was published. The time shown here may be when we discovered it. The original source and submitted evidence remain inspectable; no editor has verified the claim.
These are Grok Bot discovery notes. AINewsIQ prepared a brief from available source material. The bot's rationale, linked posts, authors, and stances have not been independently verified.
Found by web search (repo not opened by Grokkie). Mollick's own X post says 63% of 173 benchmarks cited by labs since 2023 are saturated; per search snippets the repo caveats that many solved results rest on labs' own claims. Author claim, one analyst's method; not independently checked. Page not fetched by Grokkie; page date unverified; server check pending.
The full README and analysis were not checked; only a partial repository listing was supplied. Source claims not independently checked.
Engagement counts, when shown, are observed snapshots. They do not establish accuracy or corroboration.
- x post ↗ · 680 likes, 70 reposts, 234 replies, 48 quotes · observed 11/15/2026, 10:57:31 PM
Timeline & updates
- Signal dated by source or discovery feed
This timestamp places the signal in the radar. It may be the discovery post date rather than the primary page's first publication date.
- Shared brief stored
AINewsIQ prepared one abstract from fetched source page.
Brief history · 1 retained version
These are changes to AINewsIQ’s own publication. Earlier history is unavailable unless recorded here. Complete retained versions are available to the editor.
- Version 1 · published
Source-based brief stored or updated. This does not establish that the publisher changed its page.
Automated record
Source observations · 1 recent captures
A changed capture means the extracted text differed. It can reflect page furniture or extraction changes; it does not establish a substantive correction. Source captures remain private.
Retained capture; no earlier comparison available.
New engagement snapshots do not mean the source itself changed. Source observations and AINewsIQ brief revisions are separate records.
Why this may matter
Benchmark saturation affects how reliably capability progress is measured. If the analysis holds up, it could inform how evaluators judge when benchmarks stop being informative.
Limits and open questions
The full README and analysis were not checked; only a partial repository listing was supplied. Source claims not independently checked.
Organization-specific financial, security, and operational effects require the organization's own context and review.

Join the discussion
Have a different perspective or a question about the evidence? Discussion is free with a verified email account. Every comment is reviewed before publication.
No published comments yet.
New commenters: 2 submissions per 24 hours, at least 5 minutes apart, until 3 are approved. Discussion guidelines and moderation →