Triple
T688710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Valais |
E13342
|
entity |
| Predicate | hasBorderRiver |
P225
|
FINISHED |
| Object | Rhône |
E1922
|
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: Rhône | Statement: [Valais, hasBorderRiver, Rhône]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Rhône Context triple: [Valais, hasBorderRiver, Rhône]
-
A.
Rhône
Rhône is a department in eastern France named after the Rhône River, known for its capital city Lyon and its significant role in the country's economic and cultural life.
-
B.
Rhône River
chosen
The Rhône River is a major European waterway that flows from the Swiss Alps through Lake Geneva into southeastern France, ultimately emptying into the Mediterranean Sea.
-
C.
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.
-
D.
Saône River
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.
-
E.
Ouvèze River
The Ouvèze River is a river in southeastern France that flows through the Drôme and Vaucluse departments before joining the Rhône.
- 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_69a4933e0f98819097d22766c49b61b8 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4a09669e4819089753204772e1fdd |
completed | March 1, 2026, 8:24 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a7c7074cc88190912969a1ba0a8c6e |
completed | March 4, 2026, 5:45 a.m. |
Created at: March 1, 2026, 7:36 p.m.