Triple
T23469309
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lure |
E569181
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | town of Vesoul |
—
|
NE NERFINISHED |
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: town of Vesoul | Statement: [Lure, locatedNear, town of Vesoul]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: town of Vesoul Context triple: [Lure, locatedNear, town of Vesoul]
-
A.
arrondissement of Vesoul
chosen
The arrondissement of Vesoul is an administrative district in the Haute-Saône department of eastern France, centered on the town of Vesoul and comprising numerous surrounding communes.
-
B.
Vaulx
Vaulx is a small French commune located in the Haute-Savoie department in the Auvergne-Rhône-Alpes region of southeastern France.
-
C.
Vollore-Ville
Vollore-Ville is a small commune in central France’s Puy-de-Dôme department, known for its historic château and scenic location in the Livradois-Forez area.
-
D.
Villefontaine
Villefontaine is a commune in the Isère department of southeastern France, known as a suburban town within the Grenoble urban area.
-
E.
Joux-la-Ville
Joux-la-Ville is a commune in the Yonne department of the Bourgogne-Franche-Comté region in north-central France.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e2458ebd808190b3298163132cfb0b |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a6feb5688190ad4ce42fc9590adb |
completed | April 29, 2026, 6:36 a.m. |
Created at: April 17, 2026, 5:54 p.m.