Triple

T20826205
Position Surface form Disambiguated ID Type / Status
Subject Kippenheim E512705 entity
Predicate hasNeighbouringMunicipality P224 FINISHED
Object Ettenheim 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: Ettenheim | Statement: [Kippenheim, hasNeighbouringMunicipality, Ettenheim]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ettenheim
Context triple: [Kippenheim, hasNeighbouringMunicipality, Ettenheim]
  • A. Ettenheim chosen
    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.
  • B. Dettenheim
    Dettenheim is a municipality in the Karlsruhe district of Baden-Württemberg, Germany, situated along the Pfinz river.
  • C. Entzheim
    Entzheim is a commune in northeastern France, near Strasbourg, best known for hosting Strasbourg Airport.
  • D. Emsbach
    Emsbach is a small river in Germany that flows through Hesse before joining the Lahn.
  • E. Seinsheim
    Seinsheim is a small municipality in the Kitzingen district of Bavaria, Germany, known for its rural character and Franconian wine-growing tradition.
  • 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_69e0b4ce39108190a6e8e5df4f1c8dc5 completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6c2fd8480819099930af691d97477 completed April 21, 2026, 12:21 a.m.
Created at: April 16, 2026, 12:41 p.m.