Triple

T22829197
Position Surface form Disambiguated ID Type / Status
Subject Karlsruhe district E565749 entity
Predicate contains P35 FINISHED
Object Bruchsal 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: Bruchsal | Statement: [Karlsruhe district, contains, Bruchsal]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bruchsal
Context triple: [Karlsruhe district, contains, Bruchsal]
  • A. Bruchsal chosen
    Bruchsal is a town in the state of Baden-Württemberg in southwestern Germany, known for its baroque palace and asparagus cultivation.
  • B. Fritzlar
    Fritzlar is a historic town in northern Hesse, Germany, known for its well-preserved medieval old town and its significance in early German Christian history.
  • C. Badenweiler
    Badenweiler is a spa town in southwestern Germany’s Black Forest region, known for its thermal baths and as the place where Russian writer Anton Chekhov died.
  • D. Weinsberg
    Weinsberg is a small historic town in the German state of Baden-Württemberg, known for its vineyards and the ruins of the medieval Weibertreu castle.
  • E. Rastatt
    Rastatt is a historic town in southwestern Germany, known for its Baroque architecture and its role as the site of significant early 18th-century peace negotiations.
  • 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_69e24585ab1c81909b2b5065d15805d5 completed April 17, 2026, 2:36 p.m.
NER Named-entity recognition batch_69f17e2a0e308190941064965346f890 completed April 29, 2026, 3:42 a.m.
Created at: April 17, 2026, 3:34 p.m.