False positive
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 false positive means
A false positive is a pair of records asserted to be the same entity when they are not. It and the false negative are not equally expensive. A false negative leaves two records unmerged: the cost is duplication, a second invoice, a second account, a slightly wrong customer count. A false positive merges two real companies into one: the cost is a payment to the wrong bank details, a credit limit extended to the wrong legal person, a data subject's records mixed with a stranger's, and a correction that has to be propagated to every system that consumed the merged id.
That asymmetry should drive the threshold, and often does not. Systems tuned to maximise F1 implicitly weight the two errors equally; systems tuned for a match-rate target weight false positives at zero, because a false positive still counts as a match.
False positives cluster in identifiable places, which is what makes them tractable: same-stem corporate families, franchise networks, companies sharing a registered office at an agent's address, and truncated names whose discarded tokens were the discriminating ones. A resolver that has not measured itself on a fixture containing those cases has not measured itself on the cases that matter.
Entity Bind's representative fixture is built to contain them — it is sibling-complete, so every live same-named company is pulled in — and its published false-bind count on that instrument is 0. Zero wrong bindings were observed across the historical six-shape recording and the separate domain fixture. Observed correctness was 1.0000 on accepted outcomes; this does not guarantee an error-free new workload.
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
- The accuracy methodEvery published rate with the population it was measured over, its interval and its fixture — including the input shapes that fail.Open
- How it worksThe seven-stage cascade in order, what each stage can settle on its own, and what it hands to the next.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.
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.
Over-merge
An over-merge is a cluster containing records from more than one real entity — the failure that turns two customers, two suppliers or two counterparties into one.
Precision
Precision is the share of the matches a system asserted that were correct — and it is meaningless without the share of records the system was willing to decide at all.
Confidence floor
A confidence floor is the score below which a system refuses to return a match at all, expressed as an acceptance contract rather than as a promise about accuracy.
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 →