Glossary · Decisions and evidence

Abstention

An abstention is a first-class 'we do not know' returned instead of a match: the record comes back unresolved, with a ranked shortlist, a typed reason and the column that would have decided it.
How to read this

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 decisions and evidence.

On this page
the full definition

What abstention means

An abstention is a returned decision not to decide: the system declines to bind, says why, and hands back the evidence it has rather than a guess dressed as an answer. It is a distinct return shape rather than a low-confidence match, and it is not a null, because a null tells the caller nothing about what would have helped. Almost every other entity resolver returns its best candidate with a similarity score instead, and leaves the caller to work out what to do with a 0.71.

Getting this right is mostly about what travels with the refusal. A useful abstention carries the ranked shortlist so a human can settle it in seconds, a typed reason distinguishing 'nothing found' from 'two candidates I cannot separate' from 'a dependency was unavailable', the specific column that would have decided it, and an identifier that reopens the whole decision later.

Abstention is also a commercial position. On Entity Bind an abstention costs zero credits at every stage, including the stages that spent the most getting there, so the incentive to guess is removed from the pricing as well as from the code. It is the behaviour the weakest input shape depends on: on the 317-company recording of 2026-08-29, truncated names resolved at 58.10% (61/105) — 44 of 105 come back as an abstention with a shortlist, which is the correct answer for a name whose missing tokens were the discriminating ones.

The blended rate across input shapes is 95.75%, and it should be read with its own warning: A historical 2026-08-29 blend across six input shapes in a preloaded UK catalogue. Its value depends on that mix: truncated names measured 58.10% while the blend measured 95.75%. Neither establishes the current minimum-input target.

in the running product

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.

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 free
see also

The terms next to this one

Each with its own sentence, because the next question is usually about the word beside this one.

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.

Review queue

A review queue is where records the system refused to decide are held for a human, and the quality of a resolver is largely determined by how small, how well-evidenced and how accountable that queue is.

Recall@k

Recall@k is the share of records for which the correct entity appears anywhere in the top k candidates returned by retrieval, and it is the ceiling on everything a matcher downstream can get right.

Candidate generation

Candidate generation is the retrieval step that proposes the small set of entities a record might be, and its recall is the hard ceiling on everything the rest of the pipeline can achieve.

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.

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.

Decisions and evidence

The other 8 terms on this shelf

What the system returns, what it refuses to return, and what a decision can be redeemed for afterwards.

evidence basis

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.

the ask

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 →