Triple

T5284466
Position Surface form Disambiguated ID Type / Status
Subject Theater Altenburg-Gera E119581 entity
Predicate serves P98 FINISHED
Object Altenburg E296758 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: Altenburg | Statement: [Theater Altenburg-Gera, serves, Altenburg]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Altenburg
Context triple: [Theater Altenburg-Gera, serves, Altenburg]
  • A. Altenburg chosen
    Altenburg is a historic town in eastern Thuringia, Germany, known for its playing-card tradition and as the birthplace of the card game Skat.
  • B. Kronach
    Kronach is a historic town in northern Bavaria, Germany, known for its well-preserved medieval old town and the imposing Rosenberg Fortress.
  • C. Wettin
    Wettin is a small town in Saxony-Anhalt, Germany, historically significant as the ancestral seat of the influential House of Wettin.
  • D. Rudolstadt
    Rudolstadt is a historic town in the German state of Thuringia, known for its picturesque old town, Heidecksburg Castle, and cultural festivals.
  • E. 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.
  • 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_69bd446de5648190b313a90bd96730d2 completed March 20, 2026, 12:58 p.m.
NER Named-entity recognition batch_69bd84d693288190b437955e40ad6abb completed March 20, 2026, 5:33 p.m.
NED1 Entity disambiguation (via context triple) batch_69bf9535f8008190b91cf823e9484b4e completed March 22, 2026, 7:07 a.m.
Created at: March 20, 2026, 1:52 p.m.