Over-merge
The definition as the field writes it comes first, weaknesses and all. What Entity Bind does about it comes last, in its own paragraph, so you can take one without the other. Filed under measurement.
How you tell whether any of it worked, and which numbers may not be quoted without which other numbers.
every figure, with its population →What over-merge means
Over-merging is the cluster-level form of a false positive, and it is worse than the sum of the bad decisions that caused it. One wrong edge between two clean ten-record clusters yields a twenty-record cluster in which every record now has ten wrong neighbours, and the golden record assembled from it mixes two companies' addresses, numbers and ownership.
The classic causes are structural rather than accidental: a common name matched without rarity weighting, a shared registered office at a formation agent, a group whose subsidiaries all carry the parent's name, and transitive chaining through a hub record that resembles everything.
It is also the failure that is hardest to undo. Once a merged identifier has been distributed to downstream systems, splitting it requires knowing which facts belonged to which side, and most systems did not keep that. This is the practical argument for storing decisions rather than only outcomes: a merge you can explain is a merge you can reverse.
Entity Bind guards against it in three places — rarity weighting so a common token cannot carry a decision, a contradiction guard that blocks transitive merges across conflicting strong identifiers, and the confidence floor below which no binding is representable — and it records every merge as a reversible decision with a receipt. An attributed record detaches into a fresh entity; ambiguous legacy facts and general multi-member splits fail closed rather than guessing.
Where this shows up in Entity Bind
Three pages where this term stops being vocabulary and starts changing an answer, a payload or a price.
- Precision, recall and abstentionThe precision-recall trade-off is usually described as a two-way choice, and in entity resolution that description is wrong. There is a third output — declining…Open
- CRM and RevOpsThe duplicate-account problem in a running CRM, and what a merge that should not have happened costs to unwind.Open
- The accuracy methodEvery published rate with the population it was measured over, its interval and its fixture — including the input shapes that fail.Open
The fastest way past a definition is a file: which of your rows are the same company, which of your existing matches we would not have made, and what we could not decide.
Start freeThe terms next to this one
Each with its own sentence, because the next question is usually about the word beside this one.
Fragmentation
Fragmentation is the opposite failure to over-merging: one real entity split across several clusters, so the same company is counted, contracted with or invoiced more than once.
False bind
A false bind is Entity Bind's name for the error it treats as unacceptable: a record attached to the wrong company entity and returned as a decided match.
Cluster
A cluster is the set of records a resolver has decided belong to one entity, and the object that cluster-level metrics are scored against.
B-cubed (B³)
B-cubed is a cluster-level evaluation metric that scores precision and recall from the point of view of each individual record, asking what share of its assigned cluster genuinely belongs with it and what share of its true family it was placed with.
Decision receipt
A decision receipt is the durable, retrievable record of why a particular match was made — the features, the probability, the thresholds in force, the sources cited and the version of the pipeline that decided — addressable by an identifier returned with the answer.
u-probability
The u-probability of a comparison field is the probability that the field agrees by chance given that the pair is not a match — a measure of how common a value is, and therefore of how little an agreement proves.
The other 13 terms on this shelf
How you tell whether any of it worked, and which numbers may not be quoted without which other numbers.
Internal fixtures only. The historical 2026-08-29 per-tier recording covers 317 GB companies with identifier-rich arrivals seeding the catalogue first; the context tier includes country and registered-town prose. Its legacy replay has no full-prompt-verified calls and cannot certify current calibration. The September 5 CI reports cover 1,176 labelled pairs and 705 records over 250 companies using offline stubs. These are not independent customer holdouts or live production validation; the 99% minimum-input product target remains unmet. Scope is company and organisation identity only — not people, vessels, bank-account ownership, sanctions or emissions. Results may not be used for eligibility decisions about individuals, including employment, credit and tenancy.
Start with your own company records.
Create your workspace, verify your email and run your first company file. The Free plan needs no card. Create API keys in your workspace when you need an integration.
300 credits. No card.
For a guided review of your file, explore the Merge Safety Sprint →