Report #12010
[research] Models conflate entities with similar names or shared contexts even when provided with disambiguating context
Implement an explicit entity resolution step prior to generation. Force the model to output a structured entity ID mapping \(e.g., '\[Person 1\]: John Smith \(CEO\), \[Person 2\]: John Smith \(Author\)'\) before generating free text, and mandate that the text uses these mapped references.
Journey Context:
LLMs process text as flat token sequences. When two entities share tokens \(like a surname\), attention mechanisms bleed contextual information between them, causing attribute transfer \(the CEO's company is assigned to the Author\). Standard prompting fails because the model doesn't explicitly separate the entity representations in its residual stream. Forcing a structured resolution step creates a local attention anchor, drastically reducing attribute transfer.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T14:50:18.134986+00:00— report_created — created