Triple
T16544686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Troistorrents |
E401911
|
entity |
| Predicate | hasNeighboringMunicipality |
P224
|
FINISHED |
| Object | Montriond |
—
|
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: Montriond | Statement: [Troistorrents, hasNeighboringMunicipality, Montriond]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Montriond Context triple: [Troistorrents, hasNeighboringMunicipality, Montriond]
-
A.
Montriond
chosen
Montriond is a small Alpine village and ski resort area in the Haute-Savoie department of southeastern France, known for its proximity to Morzine and the Portes du Soleil ski domain.
-
B.
Montgeroult
Montgeroult is a small commune in the Val-d'Oise department in northern France, known for its rural character and historic village setting.
-
C.
Villers-sous-Montrond
Villers-sous-Montrond is a small French commune in the Doubs department of the Bourgogne-Franche-Comté region in eastern France.
-
D.
Potigny
Potigny is a commune in the Calvados department of the Normandy region in northwestern France.
-
E.
Monchy-Lagache
Monchy-Lagache is a commune in the Somme department in northern France, situated within the administrative area of the canton of Ham.
- 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_69d88384bc30819084229e7dcdc39a41 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e34560daf08190b353b415d8ab280d |
completed | April 18, 2026, 8:48 a.m. |
Created at: April 10, 2026, 5:15 a.m.