Skip to content

    Entity Resolution

    Data integration & searchEntity dissolutionRecord LinkageReconciliation
    Editorially reviewed on: 2 sources
    Your reading view

    The short answer · 10 words

    In short

    Entity Resolution detects which records describe the same real entity.

    Flow-alerta.cab (2026): Entity Resolution. https://flow-alerta.cab/en/glossar/entity-resolution. Editorially reviewed on: 10 October 2026.

    How much detail would you like?

    Practical

    Clean entity assignment improves CRM, reporting, compliance and duplicate cleanup.

    Hypothetical example: Customer bases from CRM and ERP are compared with comprehensible match rules.

    SMEs can reduce duplicates, should provide for safe non-matches and check queues.

    At a glance

    Core
    Rules or probabilistic models compare features and decide whether different spellings or sources belong together.
    Use
    Clean entity assignment improves CRM, reporting, compliance and duplicate cleanup.
    Example
    Hypothetical example: Customer bases from CRM and ERP are compared with comprehensible match rules.
    Limits
    Incorrect and missed mergers have different costs; thresholds, data protection and manual checks must fit the purpose.

    In context

    Questions about this term

    Is Entity Resolution Just Fuzzy Matching?

    No, it combines several signals and decision rules.

    Can everything be automatically merged?

    Not without controls.

    All details and background

    Rules or probabilistic models compare features and decide whether different spellings or sources belong together.

    ELI5 – Explained simply

    It recognizes that “M.” Müller GmbH" and "Mueller GmbH" can be the same company.

    Why it matters in practice

    Clean entity assignment improves CRM, reporting, compliance and duplicate cleanup.

    Example

    Hypothetical example: Customer bases from CRM and ERP are compared with comprehensible match rules.

    Pitfalls and limits

    • Incorrect and missed mergers have different costs; thresholds, data protection and manual checks must fit the purpose.

    Origin & history

    Fellegi and Sunter formalized 1969 probabilistic record linkage with decisions for match, non-match and unclear case.

    Use in mid-sized companies

    • SMEs can reduce duplicates, should provide for safe non-matches and check queues.

    Sources

    Quellenprüfung: 10.10.2026. Definition und dokumentierte Einordnung abgeglichen; Beispiele beschreiben mögliche Anwendungen.

    Editorially reviewed on:

    Next step

    Put knowledge into practice