When the Future Has Been Stolen: A Detective Story About Prediction Authenticity
Paper: *Hindcast: Replaying Prediction Markets to Evaluate LLM Forecasters* Authors: Xiao Ye, Jacob Dineen, Evan Zhu, Shijie Lu, Kevin Song, Ben Zhou arXiv: 2607.14051 Area: NLP / AI evaluation
The Oracle's Dilemma
Like the Delphic oracle whose vague prophecies were always "confirmed" after the fact, today's evaluations of LLM forecasters may be telling us more about memory than foresight. The paper's central claim: the methods we use to evaluate AI forecasters may themselves be cheating.
Chapter 1: The Trap of Time — Two Leakage Channels
Current practice is *backtesting*: ask an AI to "pretend it's October 2024" and predict an already-settled election, then grade against the known outcome. Two leaks undermine this:
Leak 1: Retrieval
RAG-enabled models don't travel back in time — they search today's internet, which is full of post-event analysis. As the paper puts it: *"A model that retrieves can surface reports written after the event, turning forecasting into a lookup."* Forecasting becomes table lookup; divination becomes page-flipping.
Leak 2: Training Data
Even without retrieval, a model's training cutoff may already include the "future" event. Worse, *"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 exam syllabus grows every year — and the test-takers keep learning the answers in advance.
The verdict: *"Either way, the test grades recall while claiming to grade foresight."*
Chapter 2: Hindcast — The Time Capsule Approach
Hindcast's idea: don't make the AI *pretend* to stand in the past — actually lock it in a past room.
1. Pick a past time point t₀ (e.g., Oct 15, 2024) 2. Freeze a full Reddit snapshot containing only posts published before t₀ 3. Let the AI read only that frozen snapshot 4. Use real, now-resolved Polymarket markets as test questions 5. Compare AI predictions to both the actual outcomes and the market's price at that time
This closes both leaks: the frozen snapshot prevents post-event retrieval, and because the cutoff is set per market and never changes, *"the evaluation re-runs on new markets as models improve, without going stale."*
Benchmarking against the contemporaneous market price is the second stroke of cleverness: Polymarket prices embody humanity's best judgment with the information available at the time. If the AI merely reproduces market consensus, it hasn't demonstrated superior forecasting — it may have memorized it. Only systematically beating the market counts as genuine foresight.
Chapter 3: Findings and Implications
Retrieval is a double-edged sword
Once leakage is blocked, retrieval still helps — but conditionally. When Reddit already hosted substantial pre-event discussion, retrieval lets models aggregate scattered clues. But *"Where the archive carried only speculation, retrieval hurts"* — noise poisons the model. The bottleneck is often not knowing too little, but knowing too much that is wrong.
"Prediction" may be "recitation"
Hindcast suggests many celebrated "AI forecasting" results are models reciting expert consensus memorized from training data. The method doesn't rule out all LLM forecasting ability — but it shows prior evaluations couldn't distinguish genuine foresight from sophisticated recitation.
Beyond forecasting
Any time-sensitive AI evaluation must guard against future-information leakage:
- Financial forecasting: exposure to later price data?
- Medical diagnosis: later patient outcomes in training data?
- Legal analysis: knowledge of final verdicts?
- Scientific discovery: having "read" later experimental results?
Chapter 4: Philosophical Reflections
The paper revives an old distinction between Humean (inductive) prediction — extrapolating observed patterns — and causal prediction grounded in mechanisms. LLM forecasting looks closer to the first. When an LLM correctly predicts an election, is it (a) understanding political dynamics, (b) exploiting statistical associations from similar past analyses, or (c) reciting expert consensus? Hindcast's design can at least rule out (c); separating (a) from (b) will need finer experiments.
Future directions include finer time slices (days/hours), comparing information sources (Twitter vs Reddit vs news archives), multilingual prediction markets, and leakage patterns across forecast horizons.
Epilogue
Hindcast is less a technical fix than a methodological wake-up call: the most dangerous biases hide in the most basic assumptions. Before claiming AI can see the future, make sure we aren't testing its memory. True foresight should find direction in the fog of incomplete information — not pretend ignorance after already knowing the answers.
Reference
Ye, X., Dineen, J., Zhu, E., Lu, S., Song, K., & Zhou, B. (2026). Hindcast: Replaying Prediction Markets to Evaluate LLM Forecasters. *arXiv preprint* arXiv:2607.14051.