Why duplicates happen
The AI hears "the captain", "Captain Reyes" and "Reyes" across three sessions and cannot always tell they are one person — especially before any names are locked. Rather than guess, it creates separate entries and flags the pair.
Where you see them
- Session page — under the session's entities, pairs marked may be duplicate of or may refer to.
- Post-session review (
/campaigns/<your-campaign>/review) — the Possible duplicates list across the whole campaign. - Wrap-up — new entities can be sent straight to an existing one with Merge into existing.
- Entity page — Merge on any entry.
This list updates after every session you process, so it stays current.
What a merge does
You pick which entry to keep. The other entry's mentions, history and relationships move to the kept entry, and its name becomes an alias of the kept one so future mentions resolve correctly. The merged entry stops appearing in lists.
Prevention
Lock names early for your recurring cast and approve alias suggestions in wrap-up. The more names and aliases are settled, the fewer duplicates later sessions create.