Triple

T23212180
Position Surface form Disambiguated ID Type / Status
Subject Otto von Below E580625 entity
Predicate deathPlace P21 FINISHED
Object Ballenstedt 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: Ballenstedt | Statement: [Otto von Below, deathPlace, Ballenstedt]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ballenstedt
Context triple: [Otto von Below, deathPlace, Ballenstedt]
  • A. Ballenstedt chosen
    Ballenstedt is a historic town in the German state of Saxony-Anhalt, known for its castle and location on the northern edge of the Harz Mountains.
  • B. Hettstedt
    Hettstedt is a small German town in the state of Saxony-Anhalt, historically known for its copper mining and metalworking industry.
  • C. Harpstedt
    Harpstedt is a small municipality and administrative center in Lower Saxony, Germany, known for its rural character and location within the Diepholz district.
  • D. Garstedt
    Garstedt is a former independent municipality in northern Germany that now forms part of the city of Norderstedt in Schleswig-Holstein.
  • E. Athenstedt
    Athenstedt is a small village in the German state of Saxony-Anhalt.
  • 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_69e2460389408190be74f41d217799a9 completed April 17, 2026, 2:38 p.m.
NER Named-entity recognition batch_69f191620378819096362252c3b819b6 completed April 29, 2026, 5:04 a.m.
Created at: April 17, 2026, 4:07 p.m.