Preparing reversible entity-link proposals with Jev

Goal

Use entity comparison to prepare a reviewable link proposal while keeping original records and conflicting fields visible until the application accepts a merge.

Prerequisites

Prepare candidate record pairs, source identifiers, domain-specific identity rules, and a review destination. Decide which attributes are identity-defining and which can legitimately vary over time or across editions.

Steps

1. Present both records with labelled fields and provenance. Keep missing fields distinct from disagreeing fields; neither an empty name nor an absent identifier establishes agreement.

2. Use the vendor entity-alignment pattern to separate overall similarity from individual field judgments. Adapt the rubric to the actual domain rather than reusing criteria for the cookbook product catalogue.

3. Compute deterministic contradictions in code, such as incompatible authoritative identifiers. Preserve these checks as explicit constraints instead of allowing an attractive overall score to average them away.

4. Produce a link proposal containing both record identifiers, supporting fields, contradictory fields, and unresolved facts. Avoid overwriting either source record during classification.

5. Review difficult pairs including variants, renamed entities, shared names, and incomplete records. Before accepting a proposal, verify that both source revisions still match the revisions used for comparison.

Expected result

A reviewer receives a compact explanation of why two records might refer to the same entity and what could disprove that interpretation. Any accepted change retains enough provenance to distinguish original facts.

Limits and test basis

No matching accuracy or reversibility test is claimed. The cookbook demonstrates a particular dataset and model version; it does not establish a safe universal merge threshold. Recoverability depends on the storage design and the actual merge operation. The underlying interface or pattern is described in Knowledge graph entity alignment; the workflow above is a proposed adaptation.