Triple

T502603
Position Surface form Disambiguated ID Type / Status
Subject Eastern France E10430 entity
Predicate containsRiver P165 FINISHED
Object Saône E18164 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: Saône | Statement: [Eastern France, containsRiver, Saône]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Saône
Context triple: [Eastern France, containsRiver, Saône]
  • A. Saône River chosen
    The Saône River is a major waterway in eastern France that flows through cities like Lyon and Dijon before joining the Rhône River.
  • B. Isère River
    The Isère River is a significant waterway in southeastern France that flows through the Alps and the city of Grenoble before joining the Rhône.
  • C. Drôme River
    The Drôme River is a scenic waterway in southeastern France known for flowing through the Drôme department and the foothills of the Alps before joining the Rhône.
  • D. Nièvre
    Nièvre is a rural department in central France’s Bourgogne-Franche-Comté region, known for its rolling countryside, the Loire River, and its capital city Nevers.
  • E. Isère
    Isère is a department in southeastern France known for its Alpine landscapes, winter sports resorts, and the city of Grenoble.
  • 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_69a2e848adf881908e5e04f7af030093 completed Feb. 28, 2026, 1:06 p.m.
NER Named-entity recognition batch_69a2f1339748819089f89691a1698dd9 completed Feb. 28, 2026, 1:44 p.m.
NED1 Entity disambiguation (via context triple) batch_69a501bb88f88190b1de92ca77606d2f completed March 2, 2026, 3:19 a.m.
Created at: Feb. 28, 2026, 1:12 p.m.