https://www.bencode.io/categories/entityresolution/ Recent content in Entityresolution on Benny Simmonds Hugo -- 0.149.1 en-us Tue, 02 Dec 2025 09:02:00 +1100 https://www.bencode.io/posts/entity/ Tue, 02 Dec 2025 09:02:00 +1100 https://www.bencode.io/posts/entity/ <ul> <li><a href="#the-problem">The Problem</a></li> <li><a href="#solution-1-make-the-api-recordcentric-not-entitycentric">Solution 1: Make the API record‑centric, not entity‑centric</a></li> <li><a href="#solution-2-introduce-your-own-stable-external-entity-id-and-map-it-to-senzing">Solution 2: Introduce your own <em>stable</em> external Entity ID and map it to Senzing</a> <ul> <li><a href="#21-public-vs-internal-ids">2.1. Public vs internal IDs</a></li> <li><a href="#22-handling-merges">2.2. Handling merges</a></li> <li><a href="#23-handling-splits">2.3. Handling splits</a></li> <li><a href="#24-pros--cons">2.4. Pros / Cons</a></li> </ul> </li> <li><a href="#solution-3-provide-an-entity-change-feed-events-for-downstream-sync">Solution 3: Provide an entity change feed (events) for downstream sync</a> <ul> <li><a href="#31-why">3.1. Why?</a></li> <li><a href="#32-event-model">3.2. Event model</a></li> </ul> </li> <li><a href="#solution-4-treat-entity-ids-as-ephemeral-handles-with-ttl-semantics">Solution 4: Treat entity IDs as <em>ephemeral handles</em> with TTL semantics</a></li> <li><a href="#solution-5-eventsourcing--versioned-entities-for-heavy-complianceaudit-usecases">Solution 5: Event‑sourcing / versioned entities (for heavy compliance/audit use‑cases)</a></li> <li><a href="#frankenres">FrankenRes</a> <ul> <li><a href="#internals">Internals</a></li> <li><a href="#api-surface">API surface</a></li> </ul> </li> <li><a href="#detecting-splits-and-merges-with-senzing">Detecting Splits and Merges with Senzing</a> <ul> <li><a href="#what-senzing-actually-provides-the-barebones">What Senzing actually provides (the barebones)</a></li> <li><a href="#minimum-state-you-need-to-track">Minimum state you need to track</a></li> <li><a href="#robust-per-event-processing-pattern">Robust per-event processing pattern</a> <ul> <li><a href="#concurrency-safeguard">Concurrency safeguard</a></li> </ul> </li> <li><a href="#split-vs-merge-detection">Split vs Merge Detection</a> <ul> <li><a href="#detecting-splits">Detecting splits</a></li> <li><a href="#detecting-merges">Detecting merges</a></li> </ul> </li> <li><a href="#a-simplier-way">A simplier way</a></li> </ul> </li> <li><a href="#senzing-lifecycle-detector-c-implementation">Senzing Lifecycle Detector C# Implementation</a> <ul> <li><a href="#single-file-example">Single-file example</a></li> <li><a href="#usage">Usage</a></li> </ul> </li> <li><a href="#tldr">TL;DR</a></li> </ul> <h2 id="the-problem">The Problem</h2> <p>The classic entity resolution gotcha: the thing that looks like a primary key (e.g. Senzing&rsquo;s entity ID) is actually a volatile cluster ID that can legitimately change as the engine learns. Senzing explicitly says their resolved entity ID is <strong>not</strong> a globally unique persistent identifier and that it&rsquo;s just an identifier for a grouping that may be transient. (<a href="https://senzing.zendesk.com/hc/en-us/articles/4415858978067-How-does-an-Entity-ID-behave" title="How does an Entity ID behave">senzing.zendesk.com</a>)</p> https://www.bencode.io/posts/senzing/ Fri, 19 Sep 2025 09:35:00 +1000 https://www.bencode.io/posts/senzing/ <ul> <li><a href="#context">Context</a> <ul> <li><a href="#record-vs-entity-vs-relationship">Record vs Entity vs Relationship</a></li> <li><a href="#data-quality-issues-er-addresses">Data Quality Issues ER Addresses</a></li> </ul> </li> <li><a href="#senzing">Senzing</a> <ul> <li><a href="#repository">Repository</a></li> <li><a href="#key-senzing-attributes">Key Senzing Attributes</a></li> <li><a href="#resolution-concepts">Resolution Concepts</a> <ul> <li><a href="#features">Features</a></li> <li><a href="#feature-scores">Feature Scores</a></li> <li><a href="#match-levels">Match Levels</a></li> </ul> </li> </ul> </li> <li><a href="#senzing-v4-sdk-setup-on-metal">Senzing V4 SDK Setup on Metal</a> <ul> <li><a href="#native-senzing-sdk-setup">Native Senzing SDK Setup</a></li> <li><a href="#net-sdk-setup">.NET SDK Setup</a> <ul> <li><a href="#setup-local-nuget-source">Setup Local NuGet Source</a></li> </ul> </li> <li><a href="#senzing-v4-c-snippets">Senzing V4 C# Snippets</a></li> </ul> </li> <li><a href="#senzing-v4-cli-tools">Senzing V4 CLI Tools</a> <ul> <li><a href="#sz_configtool">sz_configtool</a> <ul> <li><a href="#listfeatures">listFeatures</a></li> <li><a href="#listattributes">listAttributes</a></li> <li><a href="#listrules">listRules</a></li> <li><a href="#listfragments">listFragments</a></li> <li><a href="#principles">principles</a></li> </ul> </li> <li><a href="#sz_explorer">sz_explorer</a> <ul> <li><a href="#get">get</a></li> <li><a href="#how-tree">how (tree)</a></li> </ul> </li> </ul> </li> <li><a href="#senzing-weirdness">Senzing Weirdness</a> <ul> <li><a href="#typed-models-vs-loose-json-strings">Typed models vs loose JSON strings</a></li> <li><a href="#todo">TODO</a></li> <li><a href="#info-messages-aka-sz_with_info">Info Messages aka SZ_WITH_INFO</a></li> </ul> </li> <li><a href="#senzing-best-practices">Senzing Best practices</a></li> <li><a href="#resources">Resources</a></li> </ul> <h2 id="context">Context</h2> <p>The process of identifying and linking records that refer to the same real-world entity across different data sources, even when the records contain variations, errors, or incomplete information.</p>