REVIEW 2 cited by
Monotonic Representation of Numeric Properties in Language Models
Not yet reviewed by Pith; the record is open.
This paper has not been read by Pith yet. Machine review is queued; the pith claim, tier, and objections will appear here once it completes.
SPECIMEN: schema-true, not a live event
T0 review · schema-true
One-sentence machine reading of the paper's core claim.
pith:XXXXXXXX · record.json · timestamp
read the original abstract
Language models (LMs) can express factual knowledge involving numeric properties such as Karl Popper was born in 1902. However, how this information is encoded in the model's internal representations is not understood well. Here, we introduce a simple method for finding and editing representations of numeric properties such as an entity's birth year. Empirically, we find low-dimensional subspaces that encode numeric properties monotonically, in an interpretable and editable fashion. When editing representations along directions in these subspaces, LM output changes accordingly. For example, by patching activations along a "birthyear" direction we can make the LM express an increasingly late birthyear: Karl Popper was born in 1929, Karl Popper was born in 1957, Karl Popper was born in 1968. Property-encoding directions exist across several numeric properties in all models under consideration, suggesting the possibility that monotonic representation of numeric properties consistently emerges during LM pretraining. Code: https://github.com/bheinzerling/numeric-property-repr
Forward citations
Cited by 2 Pith papers
-
Low-Rank Adapting Models for Sparse Autoencoders
LoRA fine-tuning of the language model around a fixed SAE reduces the SAE-insertion loss gap by 30-55% and matches end-to-end SAEs 2-20x faster.
-
Harmonic Loss Trains Interpretable AI Models
Harmonic loss, which scores logits by inverse Euclidean distance to class prototypes with a scale-invariant normalization, yields more interpretable class centers, reduced grokking, and faster convergence across MLPs,...
Discussion (0). Continue with ORCID to comment.