Back to Articles|Published on September 22, 2026|Updated October 28, 2026|21 min read

Reliable Context Article

Multiple Sources of Truth: An Assumption Audit

A 2026 assumption audit for multi-truth data integration, comparing LTM, MBM, and DART with worked claim matrices, omission semantics, provenance, and evaluation metrics.

By Reliable Context Research

Multiple Sources of Truth: An Assumption Audit

Summary

  1. 01Multiple sources of truth are not necessarily a defect: for set-valued attributes, truth can be a set rather than a single winning value.
  2. 02A pre-model audit tests cardinality, candidate completeness, omission semantics, coexistence, and valid time before selecting a method or metric.
  3. 03Treat silence as negative evidence only when a source had both a documented duty and opportunity to enumerate the field completely.
  4. 04Evaluate partial correctness per value and use exact-set accuracy as a strict companion rather than the sole score.
  5. 05Keep provenance and earlier states so decisions can be replayed as source reliability and truth change through time.
Inside this article
  1. 01Executive Summary
  2. 02Introduction and Background
  3. 03Defining Multiple Truths and Claim Semantics
  4. 04The Assumption Audit: A Worked Claim Matrix
  5. 05Comparing LTM, MBM, DART, and the Operational Record
  6. 06Implementation Guidance for Conflicting Data
  7. 07Data Analysis and Evidence
  8. 08Failure Cases and Deployment Tests
  9. 09Implications and Future Directions
  10. 10Frequently Asked Questions (FAQs)
  11. 11Conclusion

Executive Summary

Multiple sources of truth are not necessarily a data defect. For a set-valued attribute, such as a book's authors, a film's directors, or an organization's memberships, the truth is a set rather than a single winning value. A source may report the complete set, a correct subset, an incorrect extra value, nothing at all, or a value that was correct during another period. Under open-world semantics, an absent fact may be missing but still true [1]. Consequently, silence is negative evidence only when the source had a documented duty and opportunity to enumerate the field completely.

The pre-model audit has five questions: Is cardinality one or many? Is the candidate set complete? Does omission mean false, unknown, or out of scope? Can values coexist? At what valid time is the claim evaluated? These questions determine the appropriate claim representation and metric. A four-row worked example shows why a correct subset can have precision 1.00, recall 0.67, and F1 0.80, yet exact-set accuracy of 0. Exact-set accuracy requires the whole predicted label set to match the reference [2]. Treating the subset as wholly wrong destroys evidence of partial correctness.

Three models encode materially different assumptions. Zhao et al.'s Latent Truth Model (LTM) jointly infers truth and source quality without supervision and separates false-positive from false-negative source behavior [3]. Wang et al.'s integrated Bayesian model (MBM) represents value sets, mutual exclusion, and fine-grained copying [4]. Lin and Chen's Domain-Aware Multi-Truth Discovery (DART) estimates domain-specific expertise and permits partially correct source sets (Source: researchportal.hkust.edu.hk). None is a universal winner because each turns different observable conditions into model assumptions.

The strongest deployment decision is conditional. Use a single-value constraint only when mutual exclusion and temporal scope are established. Use per-value precision, recall, F1, coverage, and calibration for open, set-valued claims. Report exact-set accuracy as a strict companion metric, not the sole score. Preserve provenance, observation time, and earlier states because source reliability and truth can change over time [5]. PROV treats the result of each revision as a new entity [6].

1.00Precision for the worked predicted subset
0.667Recall for the worked predicted subset
0.80F1 for the worked predicted subset
0Exact-set accuracy for the worked predicted subset

Introduction and Background

The phrase multiple sources of truth in data often conflates two different situations. The first is operational duplication: several systems purport to own the same single-valued field. The second is epistemic plurality: several sources make claims about an attribute whose real answer contains multiple values, varies by domain, or changes through time. Only the first is necessarily cured by selecting one authoritative system. The second requires a claim model.

Truth discovery integrates noisy information from multiple sources while estimating source reliability [7]. Reliability is generally not known before inference [8]. This creates a coupled problem: inferred truths affect estimated reliability, and estimated reliability affects inferred truths. Majority voting avoids that coupling by weighting sources equally, but that equality is itself an assumption [7].

The central limitation of a single source of truth is therefore not canonicalization. Canonical identifiers and controlled ownership are useful. The limitation is forcing an attribute-level epistemic problem into a one-winner schema. Different names do not necessarily denote different individuals in Web Ontology Language 2 (OWL 2), so identity and distinctness require evidence rather than string comparison [1]. Conversely, related entities must not be merged merely because attributes overlap.

This report answers how to reconcile conflicting data by auditing assumptions before selecting a method. In that sense, it is a data integration assumption audit: it covers claim cardinality, missingness, mutual exclusion, provenance, temporal validity, source dependence, evaluation, and deployment evidence. It does not rank LTM, MBM, and DART on one synthetic league table because the methods solve differently specified problems.

Defining Multiple Truths and Claim Semantics

From scalar values to value sets

Let an object-attribute pair be (d=(o,a)), let (V_d) be its candidate values, and let the latent truth be a subset (T_d \subseteq V_d). A source reports a subset (C_{s,d}). A single-truth method constrains (|T_d|=1); a multi-truth method permits (|T_d|\geq 0). A formal single-claim framework can even prohibit a source from giving multiple facts for one object [9]. That is an observable modeling restriction, not a neutral default.

The set model separates three propositions that a scalar cell collapses:

  • Presence: the source explicitly claims value (v).

  • Absence: the source explicitly claims that (v) does not belong.

  • Non-observation: the source makes no claim about (v).

A source need not claim anything for every object in formal truth-discovery settings [9]. OWL's open-world assumption likewise means failure to prove a statement leaves it possibly true or false [10]. A closed-world interpretation converts every non-observation into a negative, which is appropriate only when completeness has been established for the relevant query.

Cardinality, coexistence, and time

Multi-valued does not mean that all candidates can coexist. Two coauthors can be jointly true; two mutually exclusive status values cannot be true at the same valid time. Shapes Constraint Language (SHACL) can make maximum cardinality explicit with sh:maxCount [11]. A closed SHACL shape further restricts properties to an enumerated set [11]. These are declared constraints. They cannot be inferred from a blank field.

Temporal scope supplies another dimension. Valid time is when a fact is true in the modeled world, while transaction time is when the database carries it as current [12]. Two different directors can both be correct if their validity intervals do not overlap. The W3C Provenance Data Model (PROV-DM) allows alternate entities whose temporal scopes may or may not overlap [13]. Thus temporal data and multiple valid values demand interval-aware comparison, not an undated winner.

The Assumption Audit: A Worked Claim Matrix

Assume the verified author set for one book is (T={A,B,C}). Four sources illustrate the states an integration system must preserve. Table 1 distinguishes positive claims, explicit negatives, and silence before any source-quality model is fitted.

Source rowObserved reportInterpretation if enumeration is completeInterpretation if enumeration is partialScoring consequence
S1, complete truth{A, B, C}Three positives; all other candidates negativeThree positives; other candidates unknownPrecision 1.00, recall 1.00, F1 1.00, exact set 1
S2, correct subset{A, B}A and B positive; C is an omission errorA and B positive; C unobservedPrecision 1.00, recall 0.67, F1 0.80, exact set 0
S3, incorrect extra{A, B, C, D}D is a false positiveD is a positive claim that needs adjudicationPrecision 0.75, recall 1.00, F1 0.86, exact set 0
S4, no observationnothingNegative only if S4 was obligated to enumerateUnknown or out of scopeExclude from per-source recall unless coverage was expected

The matrix exposes why an unclaimed value can mean unknown rather than false. PROV-DM permits a collection to have members beyond those asserted [13], and it separately defines an empty collection as one without members [13]. Known emptiness and unreported membership are distinct data states.

The five audit questions

Before choosing an algorithm, the evaluator should answer these questions for each attribute and source class:

  • Cardinality: Is the real-world answer constrained to zero or one, exactly one, or any finite set? A schema-level maximum is evidence; observed singularity is not.

  • Candidate completeness: Can values exist outside the enumerated candidate pool? Query completeness research explicitly allows relations to omit tuples while some query regions remain complete [14].

  • Omission semantics: Did the source assert a complete list, provide a partial list, or decline coverage? Operational databases are often neither wholly closed nor wholly open [15].

  • Mutual exclusion: Which value pairs cannot coexist at the same time? This may be global, domain-specific, or interval-specific.

  • Temporal scope: What are the observation, valid, and transaction times? PROV treats time as a critical provenance dimension [6].

When silence is negative evidence

Silence is legitimately negative only when four conditions hold: the source promises exhaustive coverage of that attribute, the object was in scope, the observation succeeded, and the snapshot is aligned to the evaluation time. If any condition fails, silence should be labeled unknown, not found, blocked, or not applicable, with a reason.

This decision matters in target use cases. Author and director lists may be intended as exhaustive but can omit contributors. Membership directories may list only current or consenting members. Adverse-event records may be bounded by reporting rules, geography, time window, and access. No entire use case is automatically open-world or closed-world. Closure attaches to a specific source, query, and time.

Treating all unknown triples as false is the closed-world assumption (Source: papers.nips.cc). Under incomplete open-world evaluation, stronger models can receive lower metric values (Source: papers.nips.cc). The audit must therefore precede both training and scoring.

Silence is legitimately negative only when four conditions hold: the source promises exhaustive coverage of that attribute, the object was in scope, the observation succeeded, and the snapshot is aligned to the evaluation time.

Comparing LTM, MBM, DART, and the Operational Record

Latent Truth Model

Zhao et al. (2012) present LTM as an unsupervised probabilistic graphical model that jointly infers true records and source quality [3]. Its key observable choice is to separate a source's false-positive and false-negative behavior [3]. That separation is useful when one source over-includes values while another systematically supplies correct subsets.

The authors describe sampling inference with linear-time complexity and a faster incremental variant [3]. They report tests on two real-world datasets [3]. In the book data, the paper reports 1,263 books, 2,420 book-author facts, 48,153 claims, and 879 bookseller sources, with 100 sampled books manually labeled [16]. The movie data contained 108,873 claims from 12 sources [16]. These are author-reported study details, not reproduced production benchmarks.

LTM's constant-quality assumption across entities is consequential [16]. If a source is excellent for one domain and weak for another, one global quality estimate can blur that structure.

Integrated Bayesian model

Wang et al. (2015) make the set of values in each claim explicit [4]. Their integrated Bayesian approach defines mutual-exclusion relations that still permit multiple true values to coexist [4]. It also proposes finer-grained copy detection [4].

Those choices address two failures of independent per-value voting. First, value pairs may constrain each other. Second, repeated claims may descend from one upstream source rather than provide independent corroboration. A copied false value can spread until it looks like a majority [17]. Correlation is broader than copying and can arise from shared extraction rules or complementary coverage [18]. Wang et al. report experiments on three real-world datasets, again as a paper result rather than an independent reproduction [4].

Domain-Aware Multi-Truth Discovery

Lin and Chen (2018) derive source expertise from information richness in different domains (Source: researchportal.hkust.edu.hk). DART also models influence among domains (Source: researchportal.hkust.edu.hk). Its partial-provider semantics do not directly treat an unclaimed value as rejected [19].

The reported book dataset had 54,591 bookseller sources and 210,206 books across 18 categories; the movie dataset drew from 15 websites [19]. Table 7 reports DARTinf-Top F1 of 0.9033 for book authors and 0.9457 for movie directors under that study's settings [19]. These values are single-paper results, not generally established production benchmarks.

Table 2 compares observable assumptions rather than ordering the options by reported score.

ApproachTruth unitOmission and error semanticsDependence or domain structureBest fit and caution
LTM, Zhao et al. (2012)Candidate values within a multi-valued recordSeparate false-positive and false-negative source qualitiesGlobal source quality across entitiesFits recurring over-claim and under-claim patterns; audit the constant-quality assumption
MBM, Wang et al. (2015)Sets of values with mutual-exclusion relationsJoint set semantics rather than isolated candidatesFine-grained source copyingFits coexisting values with logical constraints; copying evidence must be observable
DART, Lin and Chen (2018)Multi-valued claims by domainA source can be a partial provider, so silence is not direct rejectionDomain expertise and cross-domain influenceFits heterogeneous domain expertise; thin domains can destabilize estimates
PROVProvenance recordRepresents the entities, people, and processes involved in producing dataStandardized provenance representationNot a truth-discovery algorithm

PROV defines a core data model for provenance for building representations of the entities, people and processes involved in producing a piece of data or thing in the world [6].

Implementation Guidance for Conflicting Data

Represent claims before reconciling them

The minimum defensible claim record contains object identity, attribute, asserted value, claim polarity, source, source locator, observation time, valid-time interval if known, scope, and whether the source promised completeness. NIST defines provenance as a chronology of origin, development, ownership, location, and changes [20]. A URL alone is not that chronology.

For data provenance for conflicting values, retain every claim that affected the decision, not only the winner. PROV models each revision as a new entity [6]. It can also describe partial states through attributes [13]. This supports replaying what was known at a prior decision time without pretending that the older value is currently true.

Resolve identity separately from truth

Entity resolution with conflicting attributes asks whether two records describe the same real thing. Truth discovery then asks which claims about that thing should be accepted. Conflating these stages can make an attribute disagreement trigger a false split, or make a superficial match trigger a false merge. Entity resolution is inherently uncertain unless records share an identifying key or agree completely [21]. NIST similarly frames identity resolution relative to uniqueness in the population served [22].

An implementation should therefore:

  • Resolve identity with evidence: preserve aliases, keys, and ambiguity rather than letting the truth model merge records implicitly.

  • Generate candidates transparently: record which values could not enter inference because extraction or retrieval missed them.

  • Encode scope: mark whether a source covers all objects, one domain, one period, or only observed positives.

  • Test dependence: group copied, syndicated, or commonly extracted claims before interpreting agreement as corroboration.

  • Retain alternatives: keep rejected candidates and the reasons for rejection so a reviewer can reconstruct the decision.

  • Version states: separate observation time, valid time, and database transaction time.

Choose closure locally

The correct unit for closure is a query, not an entire database. For example, “all directors listed in this signed filing at its effective date” may be closed if the document is authoritative and exhaustive. “All directors discoverable on the public web” remains open. A closed result requires evidence about both membership and completeness.

Candidate generation is therefore part of evaluation. A study of truth existence reported 80,949 empty answers for flight questions whose candidate pools contained no truth [23]. A model cannot recover a value it never receives. Candidate recall must be reported alongside truth-selection quality.

Data Analysis and Evidence

Worked metrics

For the predicted subset (P={A,B}) and reference (T={A,B,C}):

  • True positives: (|P\cap T|=2).

  • False positives: (|P\setminus T|=0).

  • False negatives: (|T\setminus P|=1).

  • Precision: (2/(2+0)=1.00).

  • Recall: (2/(2+1)=0.667).

  • F1: (2PR/(P+R)=0.80).

  • Exact-set accuracy: (0), because (P\neq T).

F1 is a harmonic mean of precision and recall [2]. An F-beta score permits non-even weighting between precision and recall [24]. The application loss should determine which side receives more weight. Jaccard similarity supplies another partial-overlap score [25]. None should silently replace the application loss function.

Sensitivity to omission and candidate completeness

Suppose a source reports (A) and (B), and the system assigns each claimed value probability 0.95. The key sensitivity variable is the source's assumed false-negative rate, (q), for an omitted true value. If (C) exists in the candidate set, increasing (q) weakens the negative meaning of silence. If (C) never enters the candidate set, changing (q) cannot recover it.

Table 3 shows the decision consequences. The probabilities are illustrative assumptions, not estimates from the cited papers.

ScenarioAssumed false-negative rateCandidate completenessTreatment of omitted CRecommended evaluation
Closed enumerator0.021.00Strong negative evidencePrecision, recall, exact set, calibration
Mostly complete source0.200.95Moderate negative evidencePer-value F1 plus exact set and candidate recall
Partial provider0.600.80Weak negative evidencePositive claims, coverage, abstention, interval estimates
Unknown scopenot estimableunknownUnknown, not falseDefer model selection; collect scope evidence
Candidate omitted upstreamany valuebelow 1.00C cannot be inferredAudit retrieval and entity resolution before fusion

The sensitivity result is structural: source false-negative assumptions matter only for represented candidates. Evaluation under incomplete candidates can invert model rankings, so candidate coverage should be stratified and disclosed (Source: papers.nips.cc).

What to report

A defensible evaluation bundle includes:

  • Per-value precision, recall, and F1: rewards correct subsets and penalizes extras and omissions separately. Truth-discovery work has used all three for truth recovery [23].

  • Exact-set accuracy: strict completeness test. It returns credit only for an identical output set [26].

  • Hamming or Jaccard score: candidate-level disagreement or set overlap. Hamming distance is the proportion of disagreeing components [27].

  • Coverage and selective risk: quantify how often the model answers. Selective prediction trades coverage for accuracy [28].

  • Calibration: test whether a score of 0.8 corresponds to roughly 80 percent observed correctness [29]. Brier loss is not calibration alone because resolution and uncertainty also affect it [29].

  • Candidate recall: estimate the fraction of reference truths present before inference.

  • Source-quality error: evaluate estimated source parameters separately from recovered truths. Prior work used mean root square error for source quality [23].

  • Stratification: report results by domain, source coverage, set size, time depth, and candidate completeness.

Independent reproduction must also be distinguished from an author's experiment. ACM's reproduced-results criterion requires an independent person or team to obtain the main results [30]. The LTM, MBM, and DART figures in this report are reported results, not claims of reproduction.

Failure Cases and Deployment Tests

Candidate-set incompleteness

The most fundamental failure occurs before inference: the true value is absent from the candidate universe. No source-weight update can select it. Tests should inject held-out true values, measure candidate recall, and trace loss to retrieval, parsing, entity resolution, or access policy. A candidate generator and a truth selector need separate scorecards.

Correlated and copied sources

Duplicated sources can dominate voting before dependence is recognized [31]. Shared false values can be evidence of copying rather than independent support [32]. Deployment tests should cluster near-identical claims, trace common upstream evidence, and rerun evaluation with one representative per dependence group.

Thin domains and sparse sources

Many long-tail sources cover only one or two items, leaving little evidence for stable reliability estimates [33]. Dropping them can reduce density and coverage [33]. The appropriate response is uncertainty, hierarchical sharing, or abstention, not an unjustified precise source score.

Changing truths and stale evidence

True values and source quality can evolve. Temporal truth-discovery work separates coverage, exactness, and freshness [34]. A static model may misclassify a previously correct value as false or treat a stale source as generally unreliable. Evaluation should use validity intervals and time-sliced holdouts, then test whether source parameters drift.

Operational evidence and replay

An inference output is not yet a defensible record. The system must show which sources supported the chosen value, which alternatives remained, what was unknown, and when the decision applied. PROV allows the timing of significant events to be described, including when an entity was generated or used, or when an activity started and finished [6].

Implications and Future Directions

The unresolved problem is not simply better source weighting. It is learning or documenting the conditions under which missingness becomes evidence. A future system should estimate completeness at the source, attribute, domain, and time level, then expose the uncertainty of that estimate. It should distinguish an absent value, an explicit negation, a blocked observation, and an out-of-scope object.

Four research directions follow:

  • Joint candidate and truth evaluation: report how much truth is lost before the truth model runs, then propagate candidate uncertainty into final confidence.

  • Dependence beyond copying: model common ownership, extraction pipelines, shared primary documents, and correlated domain coverage. Source correlation is broader than direct copying [18].

  • Temporal source quality: replace one permanent reputation score with validity-aware coverage, exactness, and freshness. Source reliability has been observed to change over time [5].

  • Decision-calibrated abstention: evaluate whether confidence supports action at a declared loss threshold. Calibration asks whether predicted probabilities represent actual correctness likelihood (Source: proceedings.mlr.press).

Deployment evidence should include pre-registered assumptions, labeled closure tests, candidate-recall audits, source-dependence analyses, time-sliced evaluation, calibration curves, and replayable decisions. A comparative evaluation of 12 truth-discovery algorithms examined initialization, parameter settings, convergence, and scalability, illustrating that implementation conditions can materially shape results [35]. A production decision needs that evidence on the organization's own claim distribution, not a borrowed F1 score.

Frequently Asked Questions (FAQs)

Can an organization have more than one source of truth?

Yes, if “source of truth” means evidence sources. It should still maintain one canonical record per real entity, while preserving multiple sourced claims for set-valued, uncertain, or time-varying attributes. Canonical identity and plural evidence solve different problems.

How should conflicting data from multiple sources be reconciled?

First resolve entity identity. Then audit cardinality, candidate completeness, omission semantics, mutual exclusion, time, and source dependence. Represent positive, negative, and unobserved claims separately. Only then select a fusion method and decision threshold. Preserve rejected alternatives and their provenance.

When does a blank count as false?

Only when the source was obliged and able to provide an exhaustive value set for that object, attribute, and time. Otherwise, the blank is unknown, not found, blocked, or out of scope. Open-world semantics explicitly permit missing but true facts [1].

Which metric is best for multiple truths?

No single metric is sufficient. Use per-value precision, recall, and F1 for partial correctness; exact-set accuracy for complete-set success; candidate recall for upstream coverage; calibration for confidence; and coverage for abstention. Set F-beta weighting from the declared relative cost of extras and omissions.

When should LTM, MBM, or DART be used?

LTM is a candidate when false-positive and false-negative source tendencies are distinct but global quality is plausible. MBM is a candidate when value-set interactions, mutual exclusion, and copying are central. DART is a candidate when source expertise varies by domain and sources are partial providers. The assumption audit should reject a method whose structural premises do not match observed data.

Conclusion

Figure 01
A Defensible Integration Sequence
  1. 01Establish identity

    Establish entity identity without hiding ambiguity.

  2. 02Define constraints

    Define attribute cardinality and coexistence constraints.

  3. 03Measure candidates

    Measure candidate completeness.

  4. 04Interpret omission

    Decide when omission is negative evidence.

  5. 05Represent time

    Represent valid time, transaction time, and observation time.

  6. 06Test dependence

    Test source dependence.

Multiple sources of truth become tractable when the unit of analysis changes from a winning cell to a sourced claim. A value may be present, explicitly absent, unobserved, out of scope, or valid during another interval. The integration system must preserve those states before it estimates source reliability.

The practical sequence is straightforward. Establish entity identity without hiding ambiguity. Define attribute cardinality and coexistence constraints. Measure candidate completeness. Decide when omission is negative evidence. Represent valid time, transaction time, and observation time. Test source dependence. Then compare LTM, MBM, DART, or another method against those observable assumptions.

Evaluation must preserve partial correctness. Precision, recall, and F1 show what a correct subset recovered; exact-set accuracy tests whether the complete answer was obtained; coverage and calibration show whether confidence supports action. Source-quality estimates and truth recovery require separate evaluation. Reported paper results are useful evidence, but they are not substitutes for reproduction on the intended domain.

The durable system-of-record principle is narrower and stronger than “pick one source.” Keep one canonical record per real thing, retain every consequential claim with provenance, declare unknowns explicitly, and reproduce the state used for any decision. The model may elect a value, but the record must make that election defensible.

External Sources (35)

Published by

Reliable Context Research

Reliable Context is a system of record for organizations that fuse private and public information and must defend every value they act on: one canonical record per real thing, ambiguity shown rather than hidden, and provenance behind every value.

Our product · Evidence and editorial standards · Contact

Request access

Editorial note

Researched and written by Reliable Context Research with AI-assisted research tools; sources are cited inline and checked before publication. Report an error: https://reliablecontext.com/corrections.