Triple

T11110555
Position Surface form Disambiguated ID Type / Status
Subject Arrondissement of Liège E262742 entity
Predicate contains P35 FINISHED
Object Olne E262734 NE FINISHED

How this triple was built (2 steps)

Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.

NER Named-entity recognition gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Olne | Statement: [Arrondissement of Liège, contains, Olne]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Olne
Context triple: [Arrondissement of Liège, contains, Olne]
  • A. Olne chosen
    Olne is a small municipality in the province of Liège in Wallonia, eastern Belgium, known for its rural character and traditional village charm.
  • B. Ogna
    Ogna is a river in Trøndelag county, Norway, known for flowing through the municipality of Steinkjer.
  • C. Rissne
    Rissne is a residential district and urban area in the Stockholm metropolitan region of Sweden, known for its mix of apartment housing and proximity to public transit.
  • D. Olza River
    The Olza River is a Central European river that flows through the historical region of Cieszyn Silesia, forming part of the border between Poland and the Czech Republic.
  • E. Ognon River
    The Ognon River is a waterway in eastern France that flows through the Bourgogne-Franche-Comté region before joining the Saône River.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 batches)

The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.

Step Stage Batch ID Status When
creating Elicitation batch_69d6aa9b46cc8190b19f9f0cc45bf322 completed April 8, 2026, 7:20 p.m.
NER Named-entity recognition batch_69d79a6964508190b679303d3b3a4fd6 completed April 9, 2026, 12:24 p.m.
NED1 Entity disambiguation (via context triple) batch_69e42d759bc88190b670c373f3647a41 completed April 19, 2026, 1:18 a.m.
Created at: April 8, 2026, 9:27 p.m.