Triple

T14730843
Position Surface form Disambiguated ID Type / Status
Subject Champex-Lac E346068 entity
Predicate locatedNear P294 FINISHED
Object Orsières E1163069 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: Orsières | Statement: [Champex-Lac, locatedNear, Orsières]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Orsières
Context triple: [Champex-Lac, locatedNear, Orsières]
  • A. Orsières chosen
    Orsières is a Swiss municipality in the canton of Valais, known as a gateway to alpine passes and popular mountain tourism areas.
  • B. Olbreuse
    Olbreuse is a small locality in western France historically notable as the ancestral seat of the noble d’Olbreuse family.
  • C. Brière
    Brière is a French-language surname most prominently associated with former NHL player and current hockey executive Daniel Brière.
  • D. Valtournenche
    Valtournenche is a mountain village and commune in Italy’s Aosta Valley, known as a gateway to the Matterhorn and a popular destination for alpine climbing and skiing.
  • E. Vaujours
    Vaujours is a small suburban commune in the northeastern outskirts of Paris, France.
  • 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_69d822e5911c8190ba589f957dbd9ba7 completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69dec26311c8819093a81ff0fa43b33b completed April 14, 2026, 10:40 p.m.
NED1 Entity disambiguation (via context triple) batch_69ff4c2a938081909ccd9fe7c5021dc6 completed May 9, 2026, 3 p.m.
Created at: April 10, 2026, 1:29 a.m.