Triple

T21286943
Position Surface form Disambiguated ID Type / Status
Subject Gera–Gößnitz railway E524686 entity
Predicate endPoint P390 FINISHED
Object Gößnitz 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: Gößnitz | Statement: [Gera–Gößnitz railway, endPoint, Gößnitz]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gößnitz
Context triple: [Gera–Gößnitz railway, endPoint, Gößnitz]
  • A. Gößnitz chosen
    Gößnitz is a small town in the German state of Thuringia that lies within the broader Leipzig metropolitan area.
  • B. Brünnlitz
    Brünnlitz is a village in the Czech Republic best known as the location of Oskar Schindler’s wartime factory where he employed and saved Jewish workers during the Holocaust.
  • C. Schemnitz
    Schemnitz is the historical German name for Banská Štiavnica, a renowned medieval mining town in central Slovakia.
  • D. Premnitz
    Premnitz is a small town in the Havelland region of Brandenburg, Germany, situated on the Havel River and known historically for its chemical industry.
  • E. Harrachsdorf
    Harrachsdorf is the German name for Harrachov, a mountain town and ski resort in the Krkonoše (Giant) Mountains of the Czech Republic.
  • 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_69e0b5171f6c8190a5d57201ede73811 completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e736d717c88190950bd48058912b65 completed April 21, 2026, 8:35 a.m.
Created at: April 16, 2026, 4:03 p.m.