Triple

T21662149
Position Surface form Disambiguated ID Type / Status
Subject Neustadt bei Coburg E534619 entity
Predicate hasSubdivision P747 FINISHED
Object Ebersdorf bei Neustadt 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: Ebersdorf bei Neustadt | Statement: [Neustadt bei Coburg, hasSubdivision, Ebersdorf bei Neustadt]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ebersdorf bei Neustadt
Context triple: [Neustadt bei Coburg, hasSubdivision, Ebersdorf bei Neustadt]
  • 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. Eggersdorf
    Eggersdorf is a locality in eastern Germany known historically as the command center of the former East German Air Force.
  • C. Eltersdorf
    Eltersdorf is a district of the Bavarian city of Erlangen in Germany, known for its residential character and local transport connections.
  • D. Ernsdorf
    Ernsdorf is a small locality in Germany known primarily as the birthplace of industrialist Friedrich Flick.
  • E. Burkhardtsdorf
    Burkhardtsdorf is a small municipality in the Erzgebirge (Ore Mountains) region of Saxony, eastern 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_69e0c467e1f48190af2650b19175abc4 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69ef6c0883d481908dfdc66832c34d74 completed April 27, 2026, 2 p.m.
Created at: April 16, 2026, 6:36 p.m.