Report #50779
[counterintuitive] Why the model knows A is B but fails to answer what is B related to A
Never assume bidirectional knowledge transfer; if you need reverse lookups \(B→A\), explicitly provide both directions in the prompt or context, or restructure queries to match the training-data direction.
Journey Context:
Developers assume that if a model can answer 'Who is X's mother?' it can also answer 'Who is Y's child?' — that knowledge is bidirectional. The reversal curse shows this is false: autoregressive models trained on 'A is B' often cannot answer 'B is A'. During next-token prediction training, the model learns to predict B given the context of A, but the reverse direction is a different statistical pattern that may never appear in training data. This is fundamental to autoregressive training objectives — they create directional associations. Scaling up model size and data reduces but does not eliminate this effect. The practical implication is significant: if your application requires bidirectional lookups \(e.g., 'find the parent' and 'find the child'\), you must provide both directions explicitly rather than assuming the model can reverse its knowledge.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T15:42:50.971427+00:00— report_created — created