Triple

T21389712
Position Surface form Disambiguated ID Type / Status
Subject Reuss-Ebersdorf E527608 entity
Predicate capital P234 FINISHED
Object Ebersdorf 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 | Statement: [Reuss-Ebersdorf, capital, Ebersdorf]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ebersdorf
Context triple: [Reuss-Ebersdorf, capital, Ebersdorf]
  • 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. Hubersdorf
    Hubersdorf is a small municipality located in the canton of Solothurn in northwestern Switzerland.
  • 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. Biendorf
    Biendorf is a small municipality in northern Germany notable as the birthplace of German Field Marshal Helmuth von Moltke the Younger.
  • E. Ehrenfriedersdorf
    Ehrenfriedersdorf is a historic mining town in Saxony, Germany, known for its long tradition of tin and silver extraction in the Ore Mountains.
  • 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_69e0b51ff3748190935c0a513c62a12b completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e8b0f8ae288190b43df9fe2841a822 completed April 22, 2026, 11:28 a.m.
Created at: April 16, 2026, 5:13 p.m.