Triple

T17629491
Position Surface form Disambiguated ID Type / Status
Subject Vars E429936 entity
Predicate near P350 FINISHED
Object Col de Vars 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: Col de Vars | Statement: [Vars, near, Col de Vars]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Col de Vars
Context triple: [Vars, near, Col de Vars]
  • A. Col de Vars chosen
    Col de Vars is a high mountain pass in the French Alps, popular with cyclists and motorists for its scenic route linking the Ubaye and Queyras valleys.
  • B. Col de la Seigne
    Col de la Seigne is a high alpine pass on the border between France and Italy, known as a key crossing point on the popular Tour du Mont Blanc trekking route.
  • C. Col de Guéry
    Col de Guéry is a mountain pass in France’s Massif Central, known for its scenic views and proximity to the high-altitude Lac de Guéry.
  • D. Col de la Givrine
    Col de la Givrine is a mountain pass in the Jura Mountains of western Switzerland, known for its scenic landscapes and cross-country skiing and hiking routes.
  • E. Col de Panissars
    Col de Panissars is a mountain pass in the eastern Pyrenees on the modern French–Spanish border, historically significant as a key trans-Pyrenean route since antiquity.
  • 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_69d889e37f308190a6aa0a69daff86c7 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e46dbf59dc8190a56aa4a2449b2e2e completed April 19, 2026, 5:53 a.m.
Created at: April 10, 2026, 5:52 a.m.