Triple

T18619791
Position Surface form Disambiguated ID Type / Status
Subject Parsenn ski area E455116 entity
Predicate connects P390 FINISHED
Object Klosters 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: Klosters | Statement: [Parsenn ski area, connects, Klosters]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Klosters
Context triple: [Parsenn ski area, connects, Klosters]
  • A. Klosters chosen
    Klosters is a renowned Swiss Alpine village and ski resort in the canton of Graubünden, popular for its picturesque scenery and winter sports.
  • B. Kandersteg
    Kandersteg is a Swiss mountain village and popular tourist resort known for its scenic alpine landscapes, hiking trails, and access to Lake Oeschinen.
  • C. Arosa
    Arosa is a Swiss alpine resort town in the canton of Graubünden, known for its skiing, hiking, and scenic mountain landscapes.
  • D. Wengen
    Wengen is a car-free Swiss alpine village and popular ski and hiking resort located in the Bernese Oberland region.
  • E. Lenzerheide
    Lenzerheide is a Swiss alpine resort village known for its skiing, mountain biking, and scenic lakeside setting in the eastern Alps.
  • 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_69d8d38bbe7c8190bdec3138e7d413c9 completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e54f00889c8190931f8d3fbabd531b completed April 19, 2026, 9:54 p.m.
Created at: April 10, 2026, 11:46 a.m.