Skip to content
Meridian

Reasoning3 min read

Why long context fails quietly

By Rohan Desai, Juliette Bouchard, and Ewan Fraser

PlateContour field, seeded “why-long-context-fails-quietly”.
Contents · 5 sections

Abstract

Models with very long context windows rarely fail loudly. They answer fluently, cite plausible passages, and are wrong more often than their confidence suggests once the evidence sits deep in a long document. We trace three mechanisms behind these quiet failures in Meridian 2: positional dilution, distractor capture, and premature commitment. We then describe the changes that reduced them in Meridian 3, and the confidence signal that still does not track accuracy as well as it should.

When a model with a short context window cannot see the evidence, it usually knows. The document has been truncated, the question refers to something absent, and a reasonable model says so. Long context removes that signal. Everything is technically in view, so the model never has a reason to say it cannot find something, even when, in any practical sense, it has not.

The failure that doesn’t look like one

The failures we care about here have a specific shape. The answer is fluent. It often quotes a passage from the document, and the passage is real. The model’s stated confidence is no lower than usual. And the answer is wrong, because the quoted passage is not the one that settles the question.Note 11We call a failure quiet when the answer is wrong but its stated confidence is within five points of the model’s average on questions it gets right.

  1. 1We call a failure quiet when the answer is wrong but its stated confidence is within five points of the model’s average on questions it gets right.

These are hard to catch in practice, because every surface feature a reader might use to decide whether to double-check looks normal. They are also hard to catch in evaluation, because most long-context benchmarks score only the final answer, not whether the model’s confidence moved with its accuracy.

Three mechanisms

We studied 4,200 failures of Meridian 2 on LongTrace , a multi-hop benchmark where the evidence for each question is placed at a controlled depth in documents of up to 256K tokens. Reading transcripts and attention patterns together, we sorted most of them into three groups.

Positional dilution. Evidence in the middle of a long document is used less reliably than evidence near the start or end. This pattern has been reported for many architectures , and Meridian 2 showed it strongly.Note 22The U shape (good at the start, worse in the middle, recovering at the end) is well documented. What surprised us was how flat Meridian 2’s confidence stayed across it.

  1. 2The U shape (good at the start, worse in the middle, recovering at the end) is well documented. What surprised us was how flat Meridian 2’s confidence stayed across it.

Distractor capture. Long documents contain passages that resemble the evidence: same entities, same vocabulary, different facts. The model latches onto one of them, often because it appears earlier.Note 33LongTrace’s distractors share entities and vocabulary with the true evidence and contradict it on exactly the detail the question asks about.

  1. 3LongTrace’s distractors share entities and vocabulary with the true evidence and contradict it on exactly the detail the question asks about.

Premature commitment. The model settles on a candidate answer early in its reasoning and then stops reading later context with any care. In the attention patterns this looks like a sharp drop in reads of the remaining document once a first candidate has been written down.

Line chart: Accuracy by depth of evidence in the document.Meridian 2: 0% 79, 10% 72, 20% 61, 30% 49, 40% 40, 50% 33, 60% 29, 70% 27, 80% 30, 90% 36, 100% 47. Meridian 3: 0% 88, 10% 86, 20% 84, 30% 81, 40% 78, 50% 75, 60% 73, 70% 72, 80% 74, 90% 78, 100% 84ACCURACY20%40%60%80%100%0%10%20%30%40%50%60%70%80%90%100%Depth of evidence in the documentMeridian 2Meridian 3
Line chart: Accuracy by depth of evidence in the document.Meridian 2: 0% 79, 10% 72, 20% 61, 30% 49, 40% 40, 50% 33, 60% 29, 70% 27, 80% 30, 90% 36, 100% 47. Meridian 3: 0% 88, 10% 86, 20% 84, 30% 81, 40% 78, 50% 75, 60% 73, 70% 72, 80% 74, 90% 78, 100% 84ACCURACY20%40%60%80%100%0%20%40%60%80%100%Depth of evidence in the documentMeridian 2Meridian 3
Figure 1LongTrace accuracy by the depth of the decisive evidence, in 256K-token documents. Each point averages about 380 questions.

Measuring at depth

Figure 1 shows accuracy as a function of where the decisive evidence sits, for documents of 256K tokens. Meridian 2’s curve has the familiar dip: from 79% when the evidence is near the start, to 27% at around 70% depth, recovering to 47% at the very end. Those middle questions are the quiet failures. Meridian 2 answered them with almost exactly the same confidence it reported on questions it got right.

What we changed for Meridian 3

Three changes account for most of the improvement, and each targets one mechanism.

For dilution, we trained on long documents whose answers depend on evidence uniformly spread across depth, rather than the naturally front-loaded documents that dominate web text. This flattened the curve more than any architectural change we tried.

For distractor capture, we built training examples with deliberate near-miss passages and rewarded answers that cited the right one. This also improved citation accuracy on unrelated tasks, which we did not expect.

For premature commitment, we rewarded the model for checking at least one later passage before finalising an answer whenever the question involved more than one hop. This is crude, and it costs about 6% more tokens per answer, but it works.

Meridian 3’s curve in Figure 1 still dips, from 88% to 72%, but the dip is far shallower and the recovery nearly complete. On LongTrace overall it scores 78.4, against 41.9 for Meridian 2.

The part we haven’t fixed

Line chart: Percent by context length (tokens).Stated confidence: 8K 94, 16K 94, 32K 93, 64K 92, 128K 91, 256K 89. Accuracy: 8K 94, 16K 93, 32K 91, 64K 88, 128K 84, 256K 79PERCENT70%75%80%85%90%95%100%8K16K32K64K128K256KContext length (tokens)Stated confidenceAccuracy
Line chart: Percent by context length (tokens).Stated confidence: 8K 94, 16K 94, 32K 93, 64K 92, 128K 91, 256K 89. Accuracy: 8K 94, 16K 93, 32K 91, 64K 88, 128K 84, 256K 79PERCENT70%80%90%100%8K16K32K64K128K256KContext length (tokens)Stated confidenceAccuracy
Figure 2Meridian 3’s accuracy and mean stated confidence on LongTrace questions, by context length. The gap between them is where quiet failures live.

Accuracy improved. Calibration improved less. Figure 2 shows Meridian 3’s accuracy and its average stated confidence as the context grows. Up to 32K tokens they agree within three points. At 256K the model is about ten points more confident than it is accurate.

This matters more than the raw accuracy, because it is the gap that makes failures quiet. A model that is wrong 21% of the time at depth and says so is useful; one that is wrong 21% of the time and sounds certain is a hazard. Verbalised confidence is known to be a weak signal in general , and our results suggest it gets weaker exactly where it is most needed.

We are working on two things. The first is training the abstention objective on long documents specifically, where it was underrepresented. The second is a cheaper signal: whether the model’s answer changes when the document is reordered. Early results suggest that disagreement under reordering predicts errors at depth better than anything the model says about itself. We will report on both when we have numbers we trust.

References

  1. [1]R. Desai and J. Bouchard (2025). LongTrace: multi-hop evaluation at controlled depth. Meridian Technical Report MR-2025-11.
  2. [2]H. Varga and D. Mensah (2024). Positional effects in long-context retrieval. Findings of the Workshop on Language Modelling.
  3. [3]E. Sato and M. Lindqvist (2026). Verbalised confidence and its discontents. Proceedings of the Conference on Evaluation Methods.

All research