Correct an entity name while preserving query provenance — what should the operator record?
An ambiguous product or account name can lead to the wrong evidence set. Correcting the question is sensible, but silently changing the old table heading makes those earlier records look relevant when they may not be. Use an explicit correction branch and quarantine unresolved matches until identity is checked.
Link a corrected entity query to the original request without retroactively relabeling its records.
Store the exact original name and the interpretation that caused confusion, such as a product family mistaken for a specific model. For a model-family ambiguity, preserve the original phrase and the corrected model reference side by side; later reviewers can then understand the mistaken scope.
Keep the old query reference in lineage, remove unsupported associations from the current view and explain which rows still await identity review. The replacement table should identify which associations were corrected, while the historical error note should avoid repeating unsupported identity claims as though they remain valid.Pin the ambiguous string
Store the exact original name and the interpretation that caused confusion, such as a product family mistaken for a specific model. For a model-family ambiguity, preserve the original phrase and the corrected model reference side by side; later reviewers can then understand the mistaken scope.
Declare the intended entity
Record an explicit public reference for the intended entity and a correction_reason; do not infer private identity from similar handles. An approved entity reference should come from inspectable public evidence or the brief itself, not an assistant's confident expansion of an ambiguous abbreviation.
Tag old membership
Mark each earlier returned row confirmed-match, wrong-entity or unresolved based on inspectable evidence rather than treating every old row as invalid. Include a classification_reason and reviewer for each reassigned row; similarity in product artwork or repeated keywords is insufficient to confirm an exact variant.
Compare the corrected response
Review actual source identifiers and entity references in the corrected branch; a familiar display name alone cannot establish the match. If the corrected response repeats an old key, verify its entity association before reusing the earlier classification; recurrence alone does not resolve an ambiguous reference.
Release the corrected table
Keep the old query reference in lineage, remove unsupported associations from the current view and explain which rows still await identity review. The replacement table should identify which associations were corrected, while the historical error note should avoid repeating unsupported identity claims as though they remain valid.
Keep the boundaries clear.
- Link a corrected entity query to the original request without retroactively relabeling its records.
- Operational record: Pin the ambiguous string. Context badges do not certify access.
Start with a read-only check: ask your agent to report actual source coverage before collecting records or exporting an audience.
Primary references
Documentation reviewed 2026-11-15. Product capabilities, client availability and plans can change. Third-party marks identify their products, not an affiliation.