Triple

T19197134
Position Surface form Disambiguated ID Type / Status
Subject Zell am See E470000 entity
Predicate near P350 FINISHED
Object Kaprun 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: Kaprun | Statement: [Zell am See, near, Kaprun]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kaprun
Context triple: [Zell am See, near, Kaprun]
  • A. Kaprun chosen
    Kaprun is an Austrian alpine town known for its year-round glacier skiing, mountain scenery, and proximity to the Zell am See–Kaprun resort area.
  • B. Sölden
    Sölden is a renowned Austrian ski resort town in the Ötztal Valley, famous for its extensive alpine skiing, glacier slopes, and role as a regular FIS Alpine Ski World Cup venue.
  • C. St. Anton am Arlberg
    St. Anton am Arlberg is a renowned Austrian Alpine village and ski resort famous for its extensive slopes and vibrant après-ski scene.
  • D. Ischgl
    Ischgl is a popular Austrian ski resort town in the Paznaun Valley, renowned for its extensive slopes and lively après-ski scene.
  • E. Mayrhofen
    Mayrhofen is a popular Austrian alpine resort town known for skiing, hiking, and access to the Zillertal 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_69d8dd0ad9088190a173b32657ae2e7a completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5f8a695cc8190b84a220f52c51dfc completed April 20, 2026, 9:57 a.m.
Created at: April 10, 2026, 12:07 p.m.