Skip to content
Both Sides

Adjudication desk for contradictory data

When your sources disagree, see both sides before you pick one.

A knowledge base quietly contradicts itself all the time. Load a real entity, put every competing claim side by side with its references, and rule on which one governs with an explainable precedence engine. The ruling is sealed into a hash chain, so anyone can replay it.

Corpus source
sealed snapshot
Competing claims
111
Engine
precedence-engine@1.0.0
Agent tools
9

A live contradiction: Reykjavík · Population

Contested

45 published claims disagree about this one property. The engine ranked them on five weighted factors and returned this:

Both sides

  • 138,772LEADS64.13

    rank preferred · 1 reference

  • 107,34151.53

    rank normal · 1 reference

  • 108,48451.53

    rank normal · 1 reference

  • 109,88751.53

    rank normal · 1 reference

  • 111,54451.53

    rank normal · 1 reference

  • 112,41151.53

    rank normal · 1 reference

  • 112,55451.53

    rank normal · 1 reference

  • 113,28851.53

    rank normal · 1 reference

Showing 8 of 45 claims. See all.

Why the leader leads

Editorial rank×0.28 → 28.00

Marked preferred by the upstream editor.

Evidence depth×0.22 → 7.33

1 independent reference attached.

Corroboration×0.20 → 0.00

Second source quotes 140,000, 2,026, 252,000, none matching this claim.

Recency×0.16 → 14.80

Reference retrieved 2025-11-10 (under a year old).

Specificity×0.14 → 14.00

Exact measured quantity.

Record a ruling with a rationale, and note the losing claim. Reykjavík Population: 138772 leads 107341 by 12.60 points (A claim leads, but a rival is close enough to matter.)

Rule on this dispute

No published disputes are available yet, so this is a sealed snapshot captured 2026-10-03 from Wikidata, Wikipedia REST API, OpenStreetMap Nominatim. Import an entity to read it live.

What a visitor can actually do

  1. 01

    Import

    Search a real entity and read it live from the upstream API. Rows are validated one at a time.

  2. 02

    Inspect

    Open one property and read every competing claim, its rank, its references and its retrieval date.

  3. 03

    Rule

    Record which claim governs, with a rationale. The engine result and seal are stored with it.

  4. 04

    Export and verify

    Download Markdown or JSON, share a stable link, and replay the chain to prove nothing was edited.

Disclaimer. Both Sides ranks competing claims and records a human ruling. It does not certify that the chosen value is correct, and it is not a substitute for consulting the primary sources. Data comes from Wikidata (CC0 1.0), Wikipedia (CC BY-SA 4.0) and OpenStreetMap (ODbL).