Last confirmed
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 data, licence and time.
Facts have owners and dates. What may be stored, what may only be passed through, and what a date on a fact actually asserts.
every figure, with its population →What last confirmed means
Last confirmed is the most recent time a fact was observed still to hold. It is the field a consumer should read before relying on a value for a decision with consequences, because a fact confirmed this morning and a fact last seen in 2023 look identical unless the store records when each was last observed.
It is a weaker claim than truth. A fact confirmed last week may have changed since; the field says what was observed and when, not what is the case now. It is also distinct from a re-read: a source read again and found unchanged confirms the fact, while a source read again and found different ends one period and opens another.
Confirmation counts should distinguish repeated sightings from independent corroboration. Three reads of the same register are one source agreeing with itself; a register, a filing and a company's own website agreeing are three. Collapsing them into one counter overstates the evidence.
Entity Bind carries a last-checked timestamp and a confirmation count on every fact, keeps same-source re-confirmations separable from independent ones, and ranks survivorship on last confirmed. One thing it does not do is revalidate on a cadence: nothing is refreshed on a schedule, so a fact's freshness is the freshness of the last time a request or a snapshot happened to touch it, and the timestamp on the record states when that was rather than promising currency.
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 API referenceThe REST surface: payloads, the decision outcomes, the error model, the usage block and the ceiling on the confidence field.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.
First seen
First seen is the timestamp at which a system first observed a fact, which is evidence about the system's own history and not about when the fact became true.
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.
Survivorship
Survivorship is the set of rules that picks which value wins, field by field, when the records in a cluster disagree.
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.
Provenance
Provenance is the record of where each individual value came from — which source, retrieved when, effective when — attached to the value itself rather than to the dataset as a whole.
The other 6 terms on this shelf
Facts have owners and dates. What may be stored, what may only be passed through, and what a date on a fact actually asserts.
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 →