Triple
T1464061
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nièvre |
E31578
|
entity |
| Predicate | namedAfter |
P63
|
FINISHED |
| Object | Nièvre River |
E31578
|
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: Nièvre River | Statement: [Nièvre, namedAfter, Nièvre River]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Nièvre River Context triple: [Nièvre, namedAfter, Nièvre River]
-
A.
Nièvre
chosen
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.
-
B.
Allier River
The Allier River is a major river in central France, known for its largely unspoiled natural course and as a tributary of the Loire.
-
C.
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.
-
D.
Loir
The Loir is a river in central France that flows through the regions of Pays de la Loire and Centre-Val de Loire before joining the Sarthe.
-
E.
Yonne
Yonne is a major river in north-central France that flows through the Burgundy region before joining the Seine.
- 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_69a49917dfc081909acdbdf5d684f1ef |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c5b89708819084fb9ba4ff293b8b |
completed | March 1, 2026, 11:03 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ae7198b4948190bd37e4c27f74c817 |
completed | March 9, 2026, 7:07 a.m. |
Created at: March 1, 2026, 8 p.m.