Triple
T12385864
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vierzon |
E295861
|
entity |
| Predicate | river |
P165
|
FINISHED |
| Object | Yèvre |
E631532
|
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: Yèvre | Statement: [Vierzon, river, Yèvre]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yèvre Context triple: [Vierzon, river, Yèvre]
-
A.
Yèvre
Yèvre is a river in central France that flows through the Cher department and serves as one of its notable waterways.
-
B.
Bory
Bory is a Hungarian surname most notably associated with Jenő Bory, a sculptor, architect, and creator of the famous Bory Castle in Székesfehérvár, Hungary.
-
C.
Rybachye
Rybachye is the former name of Balykchy, a town on the western shore of Lake Issyk-Kul in Kyrgyzstan.
-
D.
Yurodivy
Yurodivy refers to the Russian tradition of "holy fools," ascetic individuals who feign madness to challenge social norms and express spiritual truths.
-
E.
Yèvre River
chosen
The Yèvre River is a waterway in central France that flows through the city of Bourges and forms part of the region’s local river network.
- 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_69d6ad9e653c8190b1473c860ee53dae |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d93fbd489c819098233a111442762e |
completed | April 10, 2026, 6:21 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f62ac939bc819081629b9eef20c4e7 |
completed | May 2, 2026, 4:48 p.m. |
Created at: April 8, 2026, 9:54 p.m.