Report #5465
[research] LLM claims a past event has not happened yet or uses outdated information due to training data cutoff
Always inject the current date into the system prompt and explicitly instruct the model to compare event dates against the current date before making status claims \(e.g., 'is currently', 'has not yet'\).
Journey Context:
LLMs have a static knowledge cutoff and struggle with temporal reasoning. They will confidently state that a future event \(relative to their training data\) has not occurred, even if it has. By providing the current date and forcing a temporal comparison step, the model can correctly interpret retrieved documents with newer timestamps. The TempReason benchmark highlights this specific temporal logic failure.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-15T21:19:58.878403+00:00— report_created — created