Triple

T22829214
Position Surface form Disambiguated ID Type / Status
Subject Karlsruhe district E565749 entity
Predicate contains P35 FINISHED
Object Dettenheim 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: Dettenheim | Statement: [Karlsruhe district, contains, Dettenheim]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Dettenheim
Context triple: [Karlsruhe district, contains, Dettenheim]
  • A. Dettenheim chosen
    Dettenheim is a municipality in the Karlsruhe district of Baden-Württemberg, Germany, situated along the Pfinz river.
  • B. Dittenheim
    Dittenheim is a small rural municipality in the Weißenburg-Gunzenhausen district of Bavaria in southern Germany.
  • C. Dossenheim
    Dossenheim is a municipality in southwestern Germany near Heidelberg, known for its agricultural research facilities and scenic location along the Bergstraße.
  • D. Ettenheim
    Ettenheim is a historic small town in southwestern Germany’s Baden-Württemberg region, known for its well-preserved old town and location near the Black Forest.
  • E. Leutesheim
    Leutesheim is a village and district of the town of Kehl in the Ortenaukreis region of Baden-Württemberg, Germany, near the Rhine River and the French border.
  • 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.