entity-resolver

Consolidates duplicate entity mentions across document corpora using fuzzy matching and confidence scoring.

4|2|Updated Jan 27, 2026
One-click install
npx skills add https://github.com/Arete-Consortium/ai-skills --skill entity-resolver-arete-consortium
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: entity-resolver
Source: https://github.com/Arete-Consortium/ai-skills/tree/main/agents/analysis/entity-resolver
Command: npx skills add https://github.com/Arete-Consortium/ai-skills --skill entity-resolver-arete-consortium

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Named entity recognition extracts entity mentions, but the same real-world person, place, or organization often appears under many spellings ("J. Smith", "John Smith", "Smith, J."), fragmenting relationship graphs and analysis. This Skill resolves that ambiguity by matching, scoring, and merging duplicate mentions into canonical entities with preserved aliases and a full audit trail. ## Core Features & Use Cases - Multi-Strategy Matching: Combines exact match, Jaccard token similarity, initial matching, Levenshtein edit distance, and phonetic (Soundex/Metaphone) matching with context boosters and reducers to compute composite confidence scores. - Conservative Merge Policy: Auto-merges only at 0.85+ confidence, routes 0.60-0.85 pairs to a human review queue, and never merges across entity types without explicit override. - Full Auditability and Reversibility: Preserves all aliases with provenance, logs every merge/split decision, and supports splitting entities when a merge is later proven wrong. - Use Case: After running NER over a new batch of legal documents, invoke resolve_entities to consolidate hundreds of name variants into canonical entities, then work through the review queue to confirm uncertain matches before building a relationship graph. ## Quick Start Ask the agent to run entity resolution on your document corpus after NER extraction, specifying the corpus ID and that uncertain matches should go to the review queue.

Frequently Asked Questions about entity-resolver

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I merge duplicate entity names across documents?▼

Run the resolve_entities operation with a corpus ID after NER extraction. The pipeline normalizes names, generates candidates using exact, Jaccard, initial, edit-distance, and phonetic matching, then auto-merges pairs scoring 0.85 or higher while queueing uncertain pairs for review.

What confidence threshold should I use for entity resolution?▼

The default auto-merge threshold is 0.85 and the review threshold is 0.60. Pairs below 0.85 are never auto-merged because false merges corrupt the entity graph and are harder to detect than false splits.

Can a wrong entity merge be reversed?▼

Yes, the split_entity operation reverses a previous merge when new evidence shows two mentions are distinct. It requires the entity ID, the aliases to separate, and a reason, and the resolution log records both the split and the original merge.

Does entity resolution handle OCR errors in scanned documents?▼

Yes, the matching pipeline is OCR-aware and accounts for common errors like rn to m, l to 1, and O to 0. Phonetic matching and edit-distance scoring help catch variants that OCR corruption would otherwise hide.

When should I not use automated entity resolution?▼

Skip it when extracting entities from raw text (use NER first), when the entity list has fewer than 10 entries (manual review is cheaper), or when entities are already canonicalized with unique IDs, since re-resolving clean data risks false merges.