Triple

T8574175
Position Surface form Disambiguated ID Type / Status
Subject Eastern Germany E203004 entity
Predicate contains P35 FINISHED
Object Chemnitz E1679 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: Chemnitz | Statement: [Eastern Germany, contains, Chemnitz]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Chemnitz
Context triple: [Eastern Germany, contains, Chemnitz]
  • A. Chemnitz chosen
    Chemnitz is a city in eastern Germany known for its industrial heritage and post-reunification urban redevelopment.
  • B. Zwickau
    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.
  • C. Zittau
    Zittau is a historic town in the southeastern corner of Germany, known for its proximity to both the Czech and Polish borders and its well-preserved medieval architecture.
  • D. Liebenwalde
    Liebenwalde is a small town and municipality in the Oberhavel district of the German state of Brandenburg.
  • E. Dresden
    Dresden is a small community within the municipality of Chatham-Kent in southwestern Ontario, Canada, known historically for its role in the Underground Railroad and Black settlement.
  • 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_69ca8328ebe481909a8c038fa79959b4 completed March 30, 2026, 2:05 p.m.
NER Named-entity recognition batch_69cbea947f188190af469babaa73ddf6 completed March 31, 2026, 3:39 p.m.
NED1 Entity disambiguation (via context triple) batch_69cf6e745864819086bab0864719ed7f completed April 3, 2026, 7:38 a.m.
Created at: March 30, 2026, 6:21 p.m.