Triple

T25361310
Position Surface form Disambiguated ID Type / Status
Subject Friedrich Wilhelm von Buxhoeveden E635973 entity
Predicate heldHighCommandDuring P145570 FINISHED
Object Napoleonic era LITERAL 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: Napoleonic era | Statement: [Friedrich Wilhelm von Buxhoeveden, heldHighCommandDuring, Napoleonic era]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: heldHighCommandDuring
Context triple: [Friedrich Wilhelm von Buxhoeveden, heldHighCommandDuring, Napoleonic era]
  • A. higherCommandDuringKoreanWar
    Indicates that one entity served as the superior command authority over another entity during the Korean War.
  • B. heldExecutivePowerUntil
    Indicates that an entity exercised executive authority or leadership in a role or office up to a specified end date or point in time.
  • C. commandingOfficerDuringEvents chosen
    Indicates that one entity served as the commanding officer of another entity during a specified set of events.
  • D. hadSecondInCommand
    Indicates that one entity had another entity serving as its second-in-command or primary subordinate leader.
  • E. higherCommandDuringVietnamWar
    Indicates that one entity served in a higher-level command role over another entity during the Vietnam War.
  • F. None of above.

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_69e75a9b7cf481909f2dcdfb37d95ca7 completed April 21, 2026, 11:08 a.m.
NER Named-entity recognition batch_69f4a10a013481908a43dd0c23917c48 completed May 1, 2026, 12:48 p.m.
PD Predicate disambiguation batch_69f45d0dbc8c8190beecce679fce90a4 completed May 1, 2026, 7:58 a.m.
Created at: April 21, 2026, 1:36 p.m.