Triple
T3107678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Savoie |
E64871
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Modane |
E55601
|
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: Modane | Statement: [Savoie, contains, Modane]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Modane Context triple: [Savoie, contains, Modane]
-
A.
Modane
chosen
Modane is a French Alpine town in the Savoie department known as a key transit point through the Fréjus Road and Rail Tunnels between France and Italy.
-
B.
La Dôle
La Dôle is a prominent mountain peak in the Jura range of western Switzerland, known for its panoramic views over Lake Geneva and the Alps and for hosting telecommunications and weather facilities near its summit.
-
C.
Mont-Dore
Mont-Dore is a spa and ski resort town in central France’s Massif Central, known for its thermal springs and access to the nearby volcanic landscapes.
-
D.
Longjumeau
Longjumeau is a suburban commune in the southern outskirts of Paris, France, known for its residential character and proximity to major transport routes.
-
E.
Olbreuse
Olbreuse is a small locality in western France historically notable as the ancestral seat of the noble d’Olbreuse family.
- 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_69ad857eeaf48190b34ebfdaa7a264cf |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada29d4aa8819093287bc71370fc05 |
completed | March 8, 2026, 4:23 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b224c4e59c819084a3aa19824c1621 |
completed | March 12, 2026, 2:28 a.m. |
Created at: March 8, 2026, 3:04 p.m.