Triple

T17818748
Position Surface form Disambiguated ID Type / Status
Subject Eilenburg E444915 entity
Predicate hasSubdivision P747 FINISHED
Object Eilenburg-Ost 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: Eilenburg-Ost | Statement: [Eilenburg, hasSubdivision, Eilenburg-Ost]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Eilenburg-Ost
Context triple: [Eilenburg, hasSubdivision, Eilenburg-Ost]
  • A. Eilenburg chosen
    Eilenburg is a small historic town in the German state of Saxony, situated on the Mulde River northeast of Leipzig.
  • B. Rüngsdorf
    Rüngsdorf is a residential district in the southern part of Bonn, Germany, known for its scenic location along the Rhine and its affiliation with the Bad Godesberg borough.
  • C. Augustdorf
    Augustdorf is a municipality in North Rhine-Westphalia, Germany, known for its proximity to the Teutoburg Forest and its significant military presence, including Bundeswehr facilities.
  • D. Elsterwerda
    Elsterwerda is a small town in the state of Brandenburg in eastern Germany, known for its regional railway connections and location near the Elbe-Elster district.
  • E. Eckental
    Eckental is a market town and municipality in the Erlangen-Höchstadt district of Bavaria, Germany.
  • 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_69d8b9f0de78819099395b14db75a8a6 completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e488812df081909771d51c54c405fe completed April 19, 2026, 7:47 a.m.
Created at: April 10, 2026, 10:15 a.m.