When the Future Has Been Stolen: A Detective Story About Forecast Evaluation
*Forum walkthrough of the paper: Hindcast: Replaying Prediction Markets to Evaluate LLM Forecasters (arXiv:2607.14051) — Xiao Ye, Jacob Dineen, Evan Zhu, Shijie Lu, Kevin Song, Ben Zhou. Field: NLP / AI evaluation.*
The Oracle's Dilemma
Just as the Delphic oracle's prophecies were so vague they could be validated after the fact, today's LLM forecasters raise a subtle problem: how do we tell genuine foresight from hindsight dressed up as prediction? The paper's core claim is that the methods we use to evaluate AI forecasters may themselves be "cheating."
Chapter 1: The Trap of Time — Two Leakage Channels
Backtesting
A common practice: pick a finished event (e.g., the November 2024 US election), ask the model "if it were October 2024, what win probability would you assign each candidate?" and score against the known outcome. This looks reasonable — but it has a fatal hole, like letting a student "pretend" not to know answers they've already seen.
Leakage channel 1: Retrieval
Modern LLMs with RAG search the *current* web — a world already full of post-election analysis. As the paper puts it: *"A model that retrieves can surface reports written after the event, turning forecasting into a lookup."* Prediction becomes lookup.
Leakage channel 2: Training data
Even without retrieval, newer models are trained on data closer to the event. The paper notes: *"Each new model is trained on data closer to the event, so a question that lay in the future for last year's models sits inside this year's training data."*
The verdict
*"Either way, the test grades recall while claiming to grade foresight."* If the evaluation methodology is systematically biased, then every claim about "AI forecasting ability" rests on unstable ground.
Chapter 2: The Hindcast Method — Freeze Time
Core idea: instead of letting the AI *pretend* to be in the past, actually confine it to the past's information.
1. Pick a past cutoff time t₀ (e.g., 2024-10-15). 2. Freeze a complete Reddit snapshot containing only posts made before t₀. 3. Allow the model to read only this frozen snapshot. 4. Use resolved Polymarket markets as test questions — markets that were genuinely trading at t₀. 5. Compare the model's predictions with (a) actual outcomes and (b) the market's contemporaneous prices, i.e., the collective human judgment at the time.
Why this works: the frozen snapshot eliminates retrieval leakage (no post-event articles can surface), and because the cutoff is fixed per market, the benchmark never goes stale — per the paper: *"Because the cutoff is set per market and the snapshot never changes, the evaluation re-runs on new markets as models improve, without going stale."*
Benchmarking against market prices also rules out another cheat: a model merely reciting the human consensus stored in its training data. Only systematic outperformance of the market would demonstrate genuine forecasting skill.
Chapter 3: Experimental Findings
- Retrieval is a double-edged sword. Once leakage is blocked, retrieval still helps most models — but only when the archive contains substantive pre-event discussion. Where the archive carried only speculation, retrieval hurts: *"Where the archive carried only speculation, retrieval hurts."* The bottleneck is often not knowing too little, but knowing too much noise.
- "Forecasting" may be "restatement." Many reported successes of LLM forecasting may just be the model reciting expert consensus memorized during training. Previous evaluation methods could not distinguish genuine prediction from sophisticated restatement.
Broader Implications
Any AI evaluation involving a time dimension must guard against future-information leakage: financial forecasting (future price data?), medical diagnosis (later patient outcomes?), legal analysis (final verdicts?), scientific discovery (results published after training?). Hindcast offers an operational template: freeze time slices and strictly bound the information.
Philosophical Coda
The paper reopens an old question: is LLM prediction Humean induction (pattern extrapolation) or causal-mechanistic understanding? When a model correctly predicts an election, has it understood political dynamics, learned statistical associations, or simply repeated expert consensus? Hindcast's design can rule out the last option; separating the first two needs finer experiments. Future directions include finer-grained time slicing (by day or hour), alternative archives (Twitter, news), multilingual prediction markets, and leakage patterns across forecast horizons.
Conclusion
Hindcast is less a technical fix than a methodological wake-up call: the most dangerous biases in AI evaluation hide in the most basic assumptions. Before claiming AI can foresee the future, make sure we are not just testing its memory. Genuine foresight should find direction in the fog of incomplete information — not pretend it never knew the answer.
Reference: Ye, X., Dineen, J., Zhu, E., Lu, S., Song, K., & Zhou, B. (2026). Hindcast: Replaying Prediction Markets to Evaluate LLM Forecasters. arXiv:2607.14051.