Triple

T19441069
Position Surface form Disambiguated ID Type / Status
Subject Aroser Rothorn E486350 entity
Predicate hasViewOf P854 FINISHED
Object Arosa 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: Arosa | Statement: [Aroser Rothorn, hasViewOf, Arosa]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Arosa
Context triple: [Aroser Rothorn, hasViewOf, Arosa]
  • A. Arosa chosen
    Arosa is a Swiss alpine resort town in the canton of Graubünden, known for its skiing, hiking, and scenic mountain landscapes.
  • B. Pontresina
    Pontresina is a Swiss alpine resort village in the canton of Graubünden, known for its scenic mountain landscapes and proximity to St. Moritz in the Upper Engadine valley.
  • C. Klosters
    Klosters is a renowned Swiss Alpine village and ski resort in the canton of Graubünden, popular for its picturesque scenery and winter sports.
  • D. Andermatt
    Andermatt is a Swiss Alpine village and ski resort in the canton of Uri, known as a major mountain transport hub and tourist destination.
  • E. Wengen
    Wengen is a car-free Swiss alpine village and popular ski and hiking resort located in the Bernese Oberland region.
  • 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_69d8e8d7ad488190a3373045029b0f3b completed April 10, 2026, 12:11 p.m.
NER Named-entity recognition batch_69e63364371081908e899c2a47af4e5d completed April 20, 2026, 2:08 p.m.
Created at: April 10, 2026, 1:38 p.m.