Triple

T2876124
Position Surface form Disambiguated ID Type / Status
Subject Chemnitz–Zwickau railway E56881 entity
Predicate terminus P388 FINISHED
Object Zwickau E102035 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: Zwickau | Statement: [Chemnitz–Zwickau railway, terminus, Zwickau]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Zwickau
Context triple: [Chemnitz–Zwickau railway, terminus, Zwickau]
  • A. Zwickau chosen
    Zwickau is a city in the German state of Saxony known historically as an important center of the automotive industry and as the birthplace of composer Robert Schumann.
  • B. Chemnitz
    Chemnitz is a city in eastern Germany known for its industrial heritage and post-reunification urban redevelopment.
  • C. Wurzen
    Wurzen is a historic town in the German state of Saxony, known for its medieval architecture and location on the river Mulde east of Leipzig.
  • D. Werdau
    Werdau is a town in the Free State of Saxony in eastern Germany, historically known for its textile and engineering industries.
  • E. Bautzen
    Bautzen is a historic town in eastern Germany known for its well-preserved medieval architecture and as a cultural center of the Sorbian minority.
  • 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_69ab4a4ced288190ab6d3e062d10f7f6 completed March 6, 2026, 9:42 p.m.
NER Named-entity recognition batch_69abe0061d048190bb1e5a01e7ceb0e2 completed March 7, 2026, 8:21 a.m.
NED1 Entity disambiguation (via context triple) batch_69badb06ddac8190a70d72b491de59c8 completed March 18, 2026, 5:04 p.m.
Created at: March 6, 2026, 10:03 p.m.