Triple

T6214706
Position Surface form Disambiguated ID Type / Status
Subject Urseren-Goms region E138956 entity
Predicate hasVillage P4011 FINISHED
Object Andermatt E425655 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: Andermatt | Statement: [Urseren-Goms region, hasVillage, Andermatt]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Andermatt
Context triple: [Urseren-Goms region, hasVillage, Andermatt]
  • A. Andermatt chosen
    Andermatt is a Swiss Alpine village and ski resort in the canton of Uri, known as a major mountain transport hub and tourist destination.
  • B. Wengen
    Wengen is a car-free Swiss alpine village and popular ski and hiking resort located in the Bernese Oberland region.
  • C. Visp
    Visp is a small town in the canton of Valais in southwestern Switzerland, situated in the Rhône valley and known as a regional transport hub and gateway to nearby Alpine resorts.
  • D. Kandersteg
    Kandersteg is a Swiss mountain village and popular tourist resort known for its scenic alpine landscapes, hiking trails, and access to Lake Oeschinen.
  • E. Gstaad
    Gstaad is an upscale Swiss alpine resort village renowned for its luxury hotels, skiing, and exclusive social scene.
  • 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_69c008ada364819096c9e92c74d639b5 completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c062a0e0488190b71b42386bacf982 completed March 22, 2026, 9:44 p.m.
NED1 Entity disambiguation (via context triple) batch_69c518ff27848190817ad516cf62c619 completed March 26, 2026, 11:31 a.m.
Created at: March 22, 2026, 4:21 p.m.