Triple

T9005001
Position Surface form Disambiguated ID Type / Status
Subject Kufstein E215120 entity
Predicate borderCrossingTo P4105 FINISHED
Object Kiefersfelden E698271 NE FINISHED

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: Kiefersfelden | Statement: [Kufstein, borderCrossingTo, Kiefersfelden]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kiefersfelden
Context triple: [Kufstein, borderCrossingTo, Kiefersfelden]
  • A. Ochsenfeld
    Ochsenfeld is a German surname most notably borne by physicist Robert Ochsenfeld, known for his work on superconductivity.
  • B. Hasselfelde
    Hasselfelde is a small town in the Harz region of central Germany, now incorporated into the municipality of Oberharz am Brocken.
  • C. Marchfeld
    Marchfeld is a fertile lowland region in eastern Austria known for its intensive agriculture and vegetable production.
  • D. Lülsfeld
    Lülsfeld is a small municipality in the Schweinfurt district of Lower Franconia in northern Bavaria, Germany.
  • E. Schneizlreuth chosen
    Schneizlreuth is a small Bavarian municipality in southeastern Germany, known for its alpine landscapes and location near the Austrian border.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 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_69ca83a12d648190b1e4fe11e8a31890 completed March 30, 2026, 2:07 p.m.
NER Named-entity recognition batch_69cc695afa34819086cf6fcce2997b5f completed April 1, 2026, 12:39 a.m.
NED1 Entity disambiguation (via context triple) batch_69d0f35010e481909efa384a314b6a45 completed April 4, 2026, 11:17 a.m.
Created at: March 30, 2026, 7:05 p.m.