Modelspublished

GPT-5 and Gemini-3 Recovered Up to 65% of Missed Facts by Thinking Longer

The Google Research and Technion benchmark shifts the diagnosis for some factual errors from missing training data to unreliable access—while leaving open whether the result holds beyond Wikipedia facts.

By 3 min read
GPT-5 and Gemini-3 Recovered Up to 65% of Missed Facts by Thinking Longer
GPT-5 and Gemini-3 Recovered Up to 65% of Missed Facts by Thinking Longer

Listen to this story

The audio brief

About 1:40
0:001:40
Read transcript
GPT-5 and Gemini-3 recovered as much as 65 percent of certain factual misses simply by thinking longer. That is the headline finding from a Google Research and Technion benchmark, and it changes how some model errors should be diagnosed. The study tested 13 language models against more than four million answers involving 2,150 Wikipedia facts. It separated two capabilities that are easy to confuse: encoding a fact, meaning the model appears to store it in the right context, and recalling it reliably when the question is phrased differently. GPT-5 and Gemini-3 encoded roughly 95 to 98 percent of the tested facts, but initially failed to recall 26 to 34 percent of those facts directly. Extra inference recovered 40 to 65 percent of the misses. In other words, some wrong answers may be lost keys, rather than empty shelves. The pattern was not universal. Scaling Gemma3 from one billion to 27 billion parameters sharply reduced encoding failures, from 85 percent to 23 percent, while recall failures still reached 40 percent. Rare facts were stored about as well as popular ones, but recall differed by more than 25 percent, and reverse-direction questions caused trouble even when models recognized equivalent answers in multiple choice. For product teams, the implication is diagnostic: try query reformulation or selective reasoning before assuming RAG is required. But reasoning costs more compute, and the benchmark is based on Wikipedia, not proprietary company data. The open question is whether WikiProfile’s distinction between missing knowledge and unreliable access holds in those settings.

Story brief

3 key points

A Google Research–Technion benchmark tested 13 models on more than 4 million answers involving 2,150 Wikipedia facts. GPT-5 and Gemini-3 encoded 95–98% of the facts, yet missed 26–34% when asked directly. Extra inference recovered 40–65% of those misses, suggesting some errors reflect retrieval difficulty rather than absent knowledge. Product teams could try query reformulation or selective reasoning before adding...

  1. 01

    Scaling Gemma3 from 1B to 27B parameters cut encoding failures from 85% to 23%, but recall failures reached 40%.

  2. 02

    Rare facts were encoded similarly to popular ones, while frontier-model recall differed by more than 25%.

  3. 03

    Models struggled with reverse-direction questions despite recognizing equivalent answers in multiple-choice formats.

A frontier model’s wrong answer may increasingly be a problem of access, not storage. A Google Research and Technion study found that extra inference-time reasoning recovered 40–65% of encoded Wikipedia facts that models initially failed to produce directly, challenging the reflex to treat every factual miss as evidence that a model needs more data or retrieval.

Stored facts and usable answers are different tests

The researchers tested 13 language models across more than 4 million responses with WikiProfile, a set of 2,150 facts drawn from Wikipedia. Their central distinction is between encoding a fact—successfully completing its original training-style context—and knowing it well enough to answer varied phrasings and directions reliably.

That framing separates two superficially identical failures. An encoding failure means the model does not reproduce the underlying information. A recall failure means it can reproduce the fact in the right context but cannot surface it for a direct question. The study also distinguishes answers recovered through thinking from answers inferred by combining other knowledge without the target fact having been explicitly encoded.

Frontier models store more than they can summon

For GPT-5 and Gemini-3, the study’s reported encoding rate was 95–98% of tested facts. That does not translate into dependable direct recall: the same frontier-model group missed 26–34% of encoded facts before being given added reasoning effort. High factual coverage and reliable generation therefore cannot be treated as the same capability.

The scaling result sharpens the contrast. Growing Gemma3 from 1 billion to 27 billion parameters reduced encoding failures from 85% to 23%, but recall failures without thinking rose as high as 40%. The finding suggests larger models can solve much of the storage problem while expanding the pool of facts that are present yet hard to retrieve on demand.

Prompt shape changes the result

The failures were not evenly distributed. Rare, long-tail facts were encoded at rates similar to popular facts, yet frontier models showed a recall gap of more than 25% between the two groups. Models also struggled with reverse questions—asking for a subject rather than an object—even when they could recognize the same answer in a multiple-choice format.

That pattern supports a narrower operational response than simply attaching retrieval-augmented generation, or RAG, to every factual task. RAG remains necessary for current information or facts absent from the model, but the study points to reformulating a query or escalating a low-confidence response to a reasoning pass when the information may already be encoded. The trade-off is compute: reasoning takes more of it than a fast direct answer.

A useful diagnostic, with a narrow evidence base

WikiProfile’s evidence is encyclopedic, not a direct test of proprietary or highly specialized company data, where storage and recall may behave differently. The article estimates a full frontier-model profile on the suite at about $500, and says teams can reduce that cost by using fewer samples or omitting multiple-choice variants. The benchmark is available through Hugging Face for teams that want to test whether their own failures are empty shelves or lost keys.

Editorial analysis

Our Read

The useful consequence is not that retrieval is obsolete. It is that teams may need to diagnose a factual miss before choosing a remedy. A system that cannot access a stored fact calls for a different intervention than one facing changing or absent information. The next meaningful test is whether custom profiles in specialized enterprise data reproduce WikiProfile’s split between high encoding and weak recall. If they do, selective retries and query reformulation may become a more central reliability layer alongside retrieval.

Citation desk / original work

Cite this

Permanent attributionView citation
Finding 01

The useful consequence is not that retrieval is obsolete.

/posts/gpt-5-and-gemini-3-recovered-up-to-65-of-missed-facts-by-thinking-longer#finding-1

Sources

  1. venturebeat.comGPT-5, Gemini-3 recall lost facts via reasoning | VentureBeat