Triple
T18467727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gex canton |
E451207
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Sauverny |
—
|
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: Sauverny | Statement: [Gex canton, contains, Sauverny]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sauverny Context triple: [Gex canton, contains, Sauverny]
-
A.
Sauverny
chosen
Sauverny is a small commune in eastern France’s Ain department, near the Swiss border and the Geneva metropolitan area.
-
B.
Souvigny
Souvigny is a historic town in central France known for its important Cluniac priory and medieval religious heritage.
-
C.
Yerville
Yerville is a small commune in the Seine-Maritime department of the Normandy region in northern France.
-
D.
Chauvigny
Chauvigny is a historic town in western France known for its medieval fortifications and picturesque setting in the Vienne department of the Nouvelle-Aquitaine region.
-
E.
Vallentigny
Vallentigny is a small French commune located in the Aube department in the Grand Est region of 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_69d8d38465a0819099b9b42d2a662ac1 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e52a8459f88190a54cae4c8cb05119 |
completed | April 19, 2026, 7:18 p.m. |
Created at: April 10, 2026, 11:34 a.m.