Triple
T11438890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Autoroute A20 |
E271084
|
entity |
| Predicate | terminusNear |
P1866
|
FINISHED |
| Object | Vierzon |
E295861
|
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: Vierzon | Statement: [Autoroute A20, terminusNear, Vierzon]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Vierzon Context triple: [Autoroute A20, terminusNear, Vierzon]
-
A.
Vierzon
chosen
Vierzon is a town in central France known historically as an industrial and railway hub in the Cher department of the Centre-Val de Loire region.
-
B.
Tournus
Tournus is a historic town in eastern France’s Burgundy region, known for its Romanesque abbey and riverside setting along the Saône.
-
C.
Soissons
Soissons is a historic town in northern France known for its strategic military importance and notable battles throughout European history.
-
D.
Saint-Dizier
Saint-Dizier is a commune in northeastern France known as an industrial town in the Haute-Marne department of the Grand Est region.
-
E.
Lubersac
Lubersac is a small commune in the Corrèze department of south-central France, known for its rural character and traditional Limousin heritage.
- 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_69d6aadeef688190874bcecd88b3dd9b |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8088711ec8190afae9f4d9f2a11ca |
completed | April 9, 2026, 8:13 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6717a5ca081908bdba9b944b76258 |
completed | May 2, 2026, 9:49 p.m. |
Created at: April 8, 2026, 9:35 p.m.