You point out another problem (from my perspective) with how we currently use the merges and matches features, Sharon.
I think many of us set a merge when we should be setting an unmerged match.
A proposed merge should mean that the research has already been done and that it indicates the 2 profiles do indeed represent the same person. A proposed merge shouldn't need additional research, just approval by the profile managers if they agree, or default approval after the wait period.
When more research is required, we should use the unmerged match to indicate that additional research is needed. That whoever sets the unmerged match should be willing to do at least some research is, of course, my personal opinion.
In your example, I would say yes, you should leave it alone (unless you plan to do the research). Without your doing any research, you have no reason to judge the merge either way.
Proposed merge, unmerged match, rejected match: whatever our actions regarding any of these states, we should define best practice to include OUR doing the requisite research before we set profiles to any of these states.