Agents Lookup

Use cases / Decision models (Jev)

Match duplicate product or customer records across lists

A cheap matcher shortlists likely twins; Jev picks the true match or 'none', and unsure pairs go to a person.

DifficultyIntermediate
Setup time3-6 hours
CategoryDecision models (Jev)

Author's figure: CodeCut author reports 807 of 808 auto-merged pairs correct with 62 sent to review, for about $0.03 on the Abt-Buy benchmark; Southbridge reports Jev plus a small review model within 0.5 points of a frontier model at a fraction of the cost.. Reported by the builder, not measured by us.

The use case

Data and ops teams merging two product catalogs, CRM exports or donor lists get many near-duplicates that fuzzy matching gets wrong. A cheap step such as embeddings shortlists a few candidates per record. Jev is asked which candidate is the same entity, or none, with rules such as 'different model numbers mean different products'. High-probability matches merge, low ones stay separate, and the middle band goes to a person. A data steward reviews that middle band and spot-checks merges before anything is deleted, because merges are hard to undo.

Example workflow

  1. Export both lists (catalog CSVs, CRM or donor records)
  2. Shortlist the 3 closest candidates per record with Sentence Transformers or RapidFuzz
  3. Ask Jev to choose the matching candidate or 'none of these', with your matching rules
  4. Merge above a high threshold, leave below a low threshold unmatched
  5. Send the middle band to a person and spot-check merges before deleting duplicates

Tools

Risks and guardrails

Sources

Written by Agents Lookup. Credits and official pages for the tools this use case names: