Provenance
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.
What the system returns, what it refuses to return, and what a decision can be redeemed for afterwards.
every figure, with its population →What provenance means
Provenance is the record of where a value came from, carried on the value itself. Dataset-level provenance ('this came from a register feed') is nearly useless operationally, because the question is always about one field. Field-level provenance ('this registered address came from the Companies House snapshot of 1 August, whose own effective date is 14 June') is what lets a consumer assess a value, dispute it, or decide it is too old for the decision at hand.
The distinction that catches people is between two clocks. The retrieval time is when we read the source; the effective date is when the source says the value was true. They are frequently months apart, and conflating them makes a freshly retrieved copy of an old value look new. A well-modelled fact carries both, and leaves the effective date null rather than defaulting it to the retrieval time when the source does not publish one.
Provenance is also the mechanism by which licence obligations survive processing. A fact whose licence forbids storage can only be handled correctly if the licence travels attached to the fact — through the survivorship rules that pick a winning value, and into anything the system writes out.
Entity Bind carries per-field provenance on every fact — source, retrieval time, the source's own effective date where it publishes one, and a licence tier — and assembles golden records with that provenance intact. Nothing is asserted without a traceable origin, and a value whose source cannot be named is not published as a fact.
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.
- Register coverageThe registers the resolver reads, the licence each one publishes under, and how often a live entity's name is unique once it is tidied to a common form.Open
- The audit packThe fixtures, the verdict logs and the replay path: what an evaluator needs to re-run a published rate for themselves.Open
- Reference dataIdentifier crosswalks, where each fact came from, and what a cited fact has to carry to be usable downstream.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.
Citation
A citation is a resolvable pointer to the specific source document or record that supports a claim, as distinct from a source name, which is only an attribution.
Temporal facts
A temporal fact is a value stored with the period over which it was true and the history of when it was observed, rather than as a single current value that silently overwrites its predecessor.
Golden record
A golden record is the single assembled view of an entity built by choosing one value per field from the records attached to it, ideally with the provenance of each choice carried alongside it.
Licence tier
A licence tier is the classification carried by an individual fact that determines what may lawfully be done with it — stored, redistributed, resold, or only shown once to the caller who asked.
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.
Survivorship
Survivorship is the set of rules that picks which value wins, field by field, when the records in a cluster disagree.
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.
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 →