Triple

T16863015
Position Surface form Disambiguated ID Type / Status
Subject BVZ Holding E409967 entity
Predicate providesServiceTo P82 FINISHED
Object Andermatt 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: Andermatt | Statement: [BVZ Holding, providesServiceTo, Andermatt]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Andermatt
Context triple: [BVZ Holding, providesServiceTo, 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. Arosa
    Arosa is a Swiss alpine resort town in the canton of Graubünden, known for its skiing, hiking, and scenic mountain landscapes.
  • D. 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.
  • E. Kandersteg
    Kandersteg is a Swiss mountain village and popular tourist resort known for its scenic alpine landscapes, hiking trails, and access to Lake Oeschinen.
  • 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_69d88395e6c88190b22730f335107c14 completed April 10, 2026, 4:59 a.m.
NER Named-entity recognition batch_69e3b50488fc8190b3b646543c3ba476 completed April 18, 2026, 4:44 p.m.
Created at: April 10, 2026, 5:24 a.m.