Candidate recall limits the best possible result
The README explains that the firm example was limited by candidate search. A correct judge cannot recover a true pair that blocking never supplied.
Inspect the supporting source ↗A record-linkage tool that asks Jev whether candidate records refer to the same entity under an explicit user-defined matching rule, then resolves links in code.
Jev judges whether two candidate records refer to the same entity under a user-supplied match definition; local code generates candidates and resolves accepted matches.
Separates blocking, pair judgments, thresholded resolution and manual audit samples so missed candidates and wrong judgments can be investigated separately.
Fixed-version documentation and implementation material were inspected on 2026-10-24. No record linkage or benchmark was rerun. Records are sent for remote scoring; anonymization and permitted data use remain application responsibilities.
Link records under an explicit definition of what counts as the same entity.
Material analysed:
The README explains that the firm example was limited by candidate search. A correct judge cannot recover a true pair that blocking never supplied.
Inspect the supporting source ↗The judge includes the supplied entity definition. Subsidiary-as-parent and typo-only matching are different tasks; one published operating point should not be copied without labels.
Inspect the supporting source ↗Useful when semantic identity matters more than string resemblance. For typo-only data, compare a simple normalized or string-similarity baseline before paying for pairwise judgments.
Read question in judge.py alongside README’s block→judge→resolve flow. Inspect an example definition and the candidate table; count how true pairs could be absent before interpreting judge accuracy.