Temporal Leakage in LLM Backtesting: Measurement, Validation, and Adjusted Scores
Not on the map. Why?
Abstract (arXiv)
The standard check for contamination in LLM backtests is simple: compare scores before and after the training cutoff. We show this check is uninformative. Four flagship models fail it on questions they cannot have memorized: every scored question resolved after their cutoffs. The reason is structural. Models legitimately know more about times near their cutoff, so recency mimics leakage, and we prove no passive backtest can separate the two from genuine skill. Measurement, not just detection, requires information from outside the backtest. We supply it in two forms. A known cutoff identifies leakage at the boundary; a matched clean control identifies it globally and yields a leakage-adjusted score. We also derive where leakage hides: it concentrates on outcomes that surprised the crowd and were well covered in training, and partial memorization is disproportionately rewarded. We validate the estimators against ground truth by planting leakage in twin models, where they recover the injected dose and return null on clean questions. Deployed on frontier models, they detect one cutoff-localized signature and, at the audit's power floor, clear five models whose apparent advantages were recency alone. Backtests need not be discarded; they need one defensible reference.
Key facts. Cited by 2 papers in the map (data through 14 Oct 2026). Builds on 41 of its 59 references that are in the map. First posted on arXiv 4 Aug 2026.
Builds on
41 of 59 references.
References · 41
- 2020Language Models are Few-Shot Learnerscited by 32,419
- 2016Membership Inference Attacks against Machine Learning Modelscited by 2,281
- 2020Extracting Training Data from Large Language Modelscited by 2,189
- 2024LiveCodeBench: Holistic and Contamination Free Evaluation of Large Language Models for Codecited by 2,004
- 2023A Survey on Hallucination in Large Language Models: Principles, Taxonomy, Challenges, and Open Questionscited by 1,601
- 2023Can LLMs Express Their Uncertainty? An Empirical Evaluation of Confidence Elicitation in LLMscited by 974
- 2023Quantifying Language Models' Sensitivity to Spurious Features in Prompt Design or: How I learned to start worrying about prompt formattingcited by 817
- 2023Detecting Pretraining Data from Large Language Modelscited by 387
- 2023NLP Evaluation in trouble: On the Need to Measure LLM Data Contamination for each Benchmarkcited by 348
- 2021Time-Aware Language Models as Temporal Knowledge Basescited by 296
- 2024LiveBench: A Challenging, Contamination-Limited LLM Benchmarkcited by 262
- 2022Data Contamination: From Memorization to Exploitationcited by 236
29 more
- 2021Mind the Gap: Assessing Temporal Generalization in Neural Language Modelscited by 230
- 2023Proving Test Set Contamination in Black Box Language Modelscited by 230
- 2023Rethinking Benchmark and Contamination for Language Models with Rephrased Samplescited by 195
- 2024Do Membership Inference Attacks Work on Large Language Models?cited by 195
- 2024A Careful Examination of Large Language Model Performance on Grade School Arithmeticcited by 191
- 2023Time Travel in LLMs: Tracing Data Contamination in Large Language Modelscited by 177
- 2024Benchmark Data Contamination of Large Language Models: A Surveycited by 147
- 2024ForecastBench: A Dynamic Benchmark of AI Forecasting Capabilitiescited by 110
- 2024Approaching Human-Level Forecasting with Language Modelscited by 107
- 2023Task Contamination: Language Models May Not Be Few-Shot Anymorecited by 99
- 2024Investigating Data Contamination for Pre-training Language Modelscited by 91
- 2024Quantifying Contamination in Evaluating Code Generation Capabilities of Language Modelscited by 65
- 2022Forecasting Future World Events with Neural Networkscited by 63
- 2024AntiLeakBench: Preventing Data Contamination by Automatically Constructing Benchmarks with Updated Real-World Knowledgecited by 44
- 2024ConStat: Performance-Based Contamination Detection in Large Language Modelscited by 33
- 2024Evaluation data contamination in LLMs: how do we measure it and (when) does it matter?cited by 32
- 2023Assessing Look-Ahead Bias in Stock Return Predictions Generated By GPT Sentiment Analysiscited by 31
- 2025Pitfalls in Evaluating Language Model Forecasterscited by 23
- 2025Hubble: a Model Suite to Advance the Study of LLM Memorizationcited by 17
- 2024Benchmark Inflation: Revealing LLM Performance Gaps Using Retro-Holdoutscited by 14
- 2026Look-Ahead-Bench: a Standardized Benchmark of Look-ahead Bias in Point-in-Time LLMs for Financecited by 13
- 2024A Comprehensive Survey of Contamination Detection Methods in Large Language Modelscited by 12
- 2025Detecting Data Contamination in LLMs via In-Context Learningcited by 8
- 2025Detecting Lookahead Bias in LLM Forecastscited by 8
- 2026DatedGPT: Preventing Lookahead Bias in Large Language Models with Time-Aware Pretrainingcited by 8
- 2024Time Machine GPTcited by 7
- 2025ExAnte: A Benchmark for Ex-Ante Inference in Large Language Modelscited by 6
- 2026All Leaks Count, Some Count More: Interpretable Temporal Contamination Detection and Mitigation in LLM Backtestingcited by 2
- 2026Summoning the Oracle to Slay It: Mitigating Look-Ahead Bias in Financial Backtesting with Large Language Modelscited by 2
Built on by
Citing papers per year: 2026: 2.
2 papers.
- 2026LLM Evaluation is a Forecasting Problemcited by 0
- 2026Auditing Future-Memory Use in Point-in-Time Language Agentscited by 0
- 2026Auditing Future-Memory Use in Point-in-Time Language Agents13 Oct 2026
- 2026LLM Evaluation is a Forecasting Problem12 Oct 2026