Glossary
Source reliability
Source reliability describes how often a source gives correct information for a defined kind of claim and context.
Truth discovery
Source reliability is a property of a source within a defined task, attribute and period, rather than a permanent verdict on an institution. A registry may be dependable for identifiers yet incomplete for operational status; a report may be accurate when published but stale later. Reliability can be measured against known answers, estimated from agreement patterns or assessed through documented editorial and collection practices.
Practitioners distinguish error from coverage. A source that rarely reports a field is not necessarily inaccurate when it does, while a source that repeats another source does not add an independent observation. Estimates also depend on case mix: performance on common entities may not carry over to obscure ones. Reliability should be revisited after a source changes ownership, collection method, scope or update cadence.
For a defensible record, the relevant question is why this source was trusted for this particular claim at this particular time. Retaining the source statement and the basis for its use makes that judgment reviewable. Source reliability informs truth discovery, but it does not by itself resolve a data conflict or prove that a specific claim is correct.
Example
A regulator feed is used for a trial identifier at Halden Therapeutics AG (fictional), while a sponsor notice is considered separately for an operational milestone.
Reliability is relative to a task
A reliability estimate answers a narrow question: how often has this source been right about this kind of claim, in this period, for this kind of subject? The answer for company identifiers may be excellent while the answer for ownership changes is poor, because the source updates one field on registration and the other only when someone files a notice. The article on source reliability by topic tests the common practice of keeping a single trust score per source and shows why a score that averages over topics hides exactly the differences a decision depends on.
Reliability also has a time dimension. A publisher that changes its collection method, merges with another or moves to automated extraction is a different source for the purposes of any estimate made before the change. Estimates should carry the window over which they were measured and should be re-run after an announced change. This is separate from the question of whether a claim was true when it was made, which is the subject of valid time.
Three ways to estimate it
The first is comparison with known answers: a sample of claims is checked against an authoritative record and the proportion correct is reported with its sampling uncertainty. This is the most direct evidence and the most expensive, so it is usually done on a stratified sample. The second is inference from agreement. Methods such as TruthFinder and the models in the survey by Li and colleagues treat a source as reliable to the extent that its claims coincide with the values that the other sources support. This works when sources err independently, and fails when they copy each other, which is why source dependence has to be modelled alongside reliability.
The third is assessment of process: documented editorial review, a stated correction policy, a registry's legal duty to be accurate, the existence of an audit. Process evidence says little about the rate of error, but it says a good deal about whether an error will be noticed and corrected, which matters for the choice of what to retain. Large-scale work such as Knowledge-Based Trust estimates the accuracy of web sources from the facts extracted from them, and it separates the errors of the extractor from the errors of the page; a reliability figure that does not make that separation will penalise a source for the extractor's mistakes.
Using the estimate without over-trusting it
An estimate is an input to a decision, not a replacement for one. A high score does not settle a data conflict in which a lower-scoring source is quoting a primary document directly, and a low score is not a reason to delete a claim that may later be corroborated. Record the score, the window and the sample size used; record also which claims it was applied to, so that the effect of a later re-estimate can be traced. The article on evaluating data sources for a knowledge graph lists the questions to put to a new source before any estimate exists, which is where most mistakes of this kind begin.
Related terms and boundaries
Reliability describes the source; source dependence describes the relation between sources; a data conflict describes the disagreement that both help to resolve. A reliable source can be wrong on an individual claim, and an unreliable source can be right, so reliability sets a prior and not a verdict. The stored claim with its provenance is what allows the prior to be revised when a source turns out to have been copying or has changed its practice. Where the question is how much to trust a language model's statement about a source, the relevant concept is faithfulness and not reliability.
Checks a reviewer can run
Ask for the estimate, the window it was measured over, the sample size and the properties it covers. Ask whether the estimate is per topic or global. Ask what happened to the estimate when the source last changed its practice. Compare the estimate with a fresh sample of twenty claims checked against a primary record. Ask whether low-scoring sources are excluded or only down-weighted, and whether any claim was dropped because of a score.
Common misreadings
- Assigning one global score to every field a source publishes.
- Mistaking broad coverage for high accuracy.
- Ignoring changes in a source over time.
Related terms
Appears in
- Majority voting vs truth discovery
A count of agreeing sources is a useful baseline; truth discovery also considers how those sources behave.
- Estimating source reliability
Assess a source for a defined property and period using checked outcomes and visible uncertainty.
References
- Li et al. (2016), A Survey on Truth Discovery, ACM SIGKDD Explorations 17(2).
- Dong et al. (2015), Knowledge-Based Trust: Estimating the Trustworthiness of Web Sources, PVLDB 8(9).
- Dong et al. (2014), Knowledge Vault: A Web-Scale Approach to Probabilistic Knowledge Fusion, KDD.
- Hogan et al. (2021), Knowledge Graphs, ACM Computing Surveys 54(4).
Found an error on this page? See corrections for what counts as one, how to report it and the dated log.
Enquiry
Where does "Source reliability" bear on a decision of yours?
This entry sits under truth discovery. If a decision in your organization turns on it, send the entity concerned, the sources you fuse to describe it and who may read which of them. We reply with what a first record would cover.
Or write to [email protected] in your own words.