Triple

T9859018
Position Surface form Disambiguated ID Type / Status
Subject Coburg district E239658 entity
Predicate contains P35 FINISHED
Object Ebersdorf bei Coburg E530521 NE FINISHED

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: Ebersdorf bei Coburg | Statement: [Coburg district, contains, Ebersdorf bei Coburg]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ebersdorf bei Coburg
Context triple: [Coburg district, contains, Ebersdorf bei Coburg]
  • A. Ebersdorf chosen
    Ebersdorf is a historic town in present-day Germany that once served as the capital of one of the small Reuss principalities.
  • B. Ebersbach (Saxony)
    Ebersbach (Saxony) is a small municipality in the German state of Saxony, situated within the central region known for its rural landscapes and historical towns.
  • C. Ebersberg
    Ebersberg is a small Bavarian town and district capital east of Munich, known for its surrounding forest and traditional Upper Bavarian character.
  • D. Oberstedten
    Oberstedten is a district of the town Oberursel in Hesse, Germany, situated near the Taunus mountain range.
  • E. Eggersdorf
    Eggersdorf is a locality in eastern Germany known historically as the command center of the former East German Air Force.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 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_69ca84e6493081909cf58c8d42ea856b completed March 30, 2026, 2:12 p.m.
NER Named-entity recognition batch_69cdb39b06b48190ab53ff00ff0513ca completed April 2, 2026, 12:08 a.m.
NED1 Entity disambiguation (via context triple) batch_69d1e43b2de881909e00f6701d1c7b54 completed April 5, 2026, 4:25 a.m.
Created at: March 30, 2026, 8:35 p.m.