Triple

T23028169
Position Surface form Disambiguated ID Type / Status
Subject Lannesdorf E573380 entity
Predicate hasNeighbouringDistrict P17964 FINISHED
Object Niederbachem 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: Niederbachem | Statement: [Lannesdorf, hasNeighbouringDistrict, Niederbachem]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Niederbachem
Context triple: [Lannesdorf, hasNeighbouringDistrict, Niederbachem]
  • A. Niederbachem chosen
    Niederbachem is a village and district of the municipality of Wachtberg in the Rhein-Sieg-Kreis of North Rhine-Westphalia, Germany.
  • B. Hemsbach
    Hemsbach is a small town in southwestern Germany, located in the Rhine-Neckar region of Baden-Württemberg.
  • C. Emsbach
    Emsbach is a small river in Germany that flows through Hesse before joining the Lahn.
  • D. Ofenbach
    Ofenbach is a French DJ and electronic music duo known for their deep house and pop-influenced dance tracks such as "Be Mine" and "Katchi."
  • E. Harmersbach
    Harmersbach is a river in the Black Forest region of Baden-Württemberg, Germany, known for flowing through the town of Zell am Harmersbach.
  • 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_69e245b821008190b0e09cb02092aae1 completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f1847f453881909a8f2affb48c64f1 completed April 29, 2026, 4:09 a.m.
Created at: April 17, 2026, 3:52 p.m.