Triple

T18053489
Position Surface form Disambiguated ID Type / Status
Subject Otto von Below E431977 entity
Predicate memberOf P10 FINISHED
Object Prussian Army officer corps NE NERFINISHED

How this triple was built (3 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: Prussian Army officer corps | Statement: [Otto von Below, memberOf, Prussian Army officer corps]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Prussian Army officer corps
Context triple: [Otto von Below, memberOf, Prussian Army officer corps]
  • A. German Army officer corps
    The German Army officer corps was the professional cadre of commissioned leaders in Germany’s land forces, central to planning and executing military operations, particularly during the World Wars.
  • B. Prussian Ministry of War
    The Prussian Ministry of War was the central government department responsible for overseeing the organization, administration, and operations of the Prussian Army.
  • C. Prussian General Staff
    The Prussian General Staff was the pioneering 19th-century military planning and command institution of the Kingdom of Prussia that became a model for modern professional general staffs worldwide.
  • D. Bavarian General Staff
    The Bavarian General Staff was the central military planning and command body of the Kingdom of Bavaria, responsible for strategic operations, organization, and leadership of its armed forces.
  • E. German General Staff
    The German General Staff was the central planning and command organization of the German Army, renowned for its highly professional, systematic approach to military strategy and operations from the 19th century through World War II.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07
Target entity: Prussian Army officer corps
Target entity description: The Prussian Army officer corps was the elite, highly professional leadership cadre of the Prussian (and later German) military, renowned for its rigorous training, discipline, and decisive influence on European warfare and state policy.
  • A. German Army officer corps
    The German Army officer corps was the professional cadre of commissioned leaders in Germany’s land forces, central to planning and executing military operations, particularly during the World Wars.
  • B. Prussian Ministry of War
    The Prussian Ministry of War was the central government department responsible for overseeing the organization, administration, and operations of the Prussian Army.
  • C. Prussian General Staff
    The Prussian General Staff was the pioneering 19th-century military planning and command institution of the Kingdom of Prussia that became a model for modern professional general staffs worldwide.
  • D. Bavarian General Staff
    The Bavarian General Staff was the central military planning and command body of the Kingdom of Bavaria, responsible for strategic operations, organization, and leadership of its armed forces.
  • E. German General Staff
    The German General Staff was the central planning and command organization of the German Army, renowned for its highly professional, systematic approach to military strategy and operations from the 19th century through World War II.
  • F. None of above. chosen

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_69d8b906482481908183315b9ecf9994 completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4c100e7e4819084470c5b7fced334 completed April 19, 2026, 11:48 a.m.
Created at: April 10, 2026, 10:26 a.m.