Triple

T23026537
Position Surface form Disambiguated ID Type / Status
Subject Stecknadelhorn E573328 entity
Predicate nearestLocality P21721 FINISHED
Object Grächen 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: Grächen | Statement: [Stecknadelhorn, nearestLocality, Grächen]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Grächen
Context triple: [Stecknadelhorn, nearestLocality, Grächen]
  • A. Grächen chosen
    Grächen is a Swiss alpine village and popular family-friendly holiday resort in the canton of Valais, known for its scenic mountain setting and access to hiking and skiing.
  • B. Goldach
    Goldach is a municipality in northeastern Switzerland, located on the southern shore of Lake Constance in the canton of St. Gallen.
  • C. Rottenegg
    Rottenegg is a small village that forms one of the local subdivisions of the Bavarian town of Geisenfeld in Germany.
  • D. Granschütz
    Granschütz is a locality in eastern Germany situated within the broader Leipzig metropolitan region.
  • E. Ophasselt
    Ophasselt is a village in the Flemish province of East Flanders, Belgium, known as one of the constituent communities of the city of Geraardsbergen.
  • 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_69e245b821008190b0e09cb02092aae1 completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f1847d7cb48190902169813c46a278 completed April 29, 2026, 4:09 a.m.
Created at: April 17, 2026, 3:52 p.m.