PRISM Edit: One Vector for All Temporal Answers

Chen Huang, Qi Zheng, Ruiqin Zheng, Long Zeng, Yuantong Xu
7/13/2026
cs.LGcs.AI

Official code: AnonymousStudy972/PRISM-Edit (1 star, MIT, last commit 2026-06-12).

Abstract

Model editing keeps large language models (LLMs) up to date without retraining, but temporal facts expose a limitation of the prevailing locate-and-edit paradigm: an update is not always a replacement. When a fact changes, the new answer should become current while the old answer may remain correct in historical time contexts. Building on this insight, we use causal tracing to show that LLMs already support this distinction via a two-stage internal computation: early MLP layers retrieve a time-agnostic subject representation, and later layers modulate it with temporal context to yield the time-correct answer. Motivated by this finding, we introduce PRISM Edit, which optimizes a single polysemous representation across temporal contexts and leverages the model's inherent modulation pathway to route it to temporally correct predictions, without any architectural modification. We evaluate on TimeConflict, a new temporal editing benchmark we introduce, and on temporally augmented CounterFact. PRISM Edit improves over the best baseline by +23.3 Temporal Consistency (TC) and +33.7 Current Relative-time Score (CRS) on average while being more than 2x faster. Code and data are publicly available at https://github.com/AnonymousStudy972/PRISM-Edit.

View on arXivView PDF

Code Implementations(1)

MIT

Code and data for "PRISM Edit: One Vector for All Temporal Answers".

10PythonJun 10, 20264 months agoMIT

Cite this paper

@article{huang2026prism,
  title  = {PRISM Edit: One Vector for All Temporal Answers},
  author = {Chen Huang and Qi Zheng and Ruiqin Zheng and Long Zeng and Yuantong Xu},
  year   = {2026},
  eprint = {2607.11327},
  archivePrefix = {arXiv},
  url    = {http://arxiv.org/abs/2607.11327v1}
}

Add a badge to your README

Shows whether official code is linked for this paper.

Code of Paper badge
[![Code of Paper](https://codeofpaper.com/badge/2607.11327.svg)](https://codeofpaper.com/paper/2607.11327)

Discussion