Triple

T19193932
Position Surface form Disambiguated ID Type / Status
Subject Karwendeltal E469915 entity
Predicate accessPoint P1985 FINISHED
Object Scharnitz 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: Scharnitz | Statement: [Karwendeltal, accessPoint, Scharnitz]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Scharnitz
Context triple: [Karwendeltal, accessPoint, Scharnitz]
  • A. Scharnitz chosen
    Scharnitz is a village in the Austrian state of Tyrol that serves as a gateway to the Karwendel mountain range and the Karwendel Alpine Park.
  • B. Gloggnitz
    Gloggnitz is a town in Lower Austria known as a gateway to the Semmering region and an important stop on the historic Southern Railway line.
  • C. Reischach
    Reischach is a municipality in Bavaria, Germany, situated within the district of Altötting.
  • D. Mörtschach
    Mörtschach is a small municipality in the Austrian state of Carinthia, situated in the Alpine region of the Möll Valley.
  • E. Feistritz an der Drau
    Feistritz an der Drau is a small Austrian town in the state of Carinthia, situated along the Drau (Drava) River and known for its scenic Alpine surroundings.
  • 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_69e5f8a409948190a17aa28a6e9c8844 completed April 20, 2026, 9:57 a.m.
Created at: April 10, 2026, 12:07 p.m.