What ambiguity should and should not imply
Ambiguity can mean the records need closer review, but it does not automatically prove the data is unusable, that a merge is obviously wrong, or that the household interpretation is already settled behind the scenes.
Likely duplicates and unclear household signals should stay visible as uncertainty until your team can explain the relationship clearly enough for the real consequence involved.
How to avoid silent certainty
Do not turn partial overlap, matching names, or familiar staff assumptions into silent proof that two records should become one or that a household boundary is already confirmed.
The safer posture is to keep the ambiguity legible, explain what is still unclear, and avoid cleanup language that sounds stronger than the record truth you actually have.