Triple

T18126869
Position Surface form Disambiguated ID Type / Status
Subject Montana E433898 entity
Predicate locatedNear P294 FINISHED
Object Crans 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: Crans | Statement: [Montana, locatedNear, Crans]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Crans
Context triple: [Montana, locatedNear, Crans]
  • A. Crans-Montana
    Crans-Montana is a renowned Swiss Alpine resort town known for its skiing, golf courses, and panoramic views of the Valais Alps.
  • B. Crans-près-Céligny chosen
    Crans-près-Céligny is a Swiss lakeside municipality in the canton of Vaud, known for its scenic location on the shores of Lake Geneva near the city of Nyon.
  • C. Gstaad
    Gstaad is an upscale Swiss alpine resort village renowned for its luxury hotels, skiing, and exclusive social scene.
  • D. Nyons
    Nyons is a small town in southeastern France renowned for its olive production and picturesque setting in the Drôme Provençale region.
  • E. Cran-Gevrier
    Cran-Gevrier is a suburban district and former commune in southeastern France, now part of the city of Annecy in the Haute-Savoie department.
  • 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_69d8b909e8cc81908df4cc2b8ea6d11f completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4ddef4cd88190b16ef0d6ed3968c6 completed April 19, 2026, 1:51 p.m.
Created at: April 10, 2026, 10:29 a.m.