Triple

T37808997
Position Surface form Disambiguated ID Type / Status
Subject Battle of Opequon E942582 entity
Predicate ConfederateDivisionCommander P26186 FINISHED
Object John B. Gordon 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: John B. Gordon | Statement: [Battle of Opequon, ConfederateDivisionCommander, John B. Gordon]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: ConfederateDivisionCommander
Context triple: [Battle of Opequon, ConfederateDivisionCommander, John B. Gordon]
  • A. ConfederateSubordinateCommander
    Indicates that one military commander served in a subordinate role under another within the Confederate forces.
  • B. primaryConfederateCommander
    Indicates that one entity serves as the main commanding officer of Confederate forces for the other entity in a specific context or engagement.
  • C. commandingConfederateForces chosen
    Indicates that one entity holds the role or responsibility of directing and leading the military operations of the Confederate forces in relation to another entity.
  • D. notableUnitConfederate
    Indicates that an entity is notably associated with a specific military unit that served in the Confederate forces.
  • E. commanderDuringAtlantaCampaign
    Indicates that one entity served as the military commander of the other entity specifically during the Atlanta Campaign.
  • 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_69f76ee8104c8190ab17133ccd8f86e6 completed May 3, 2026, 3:51 p.m.
NER Named-entity recognition batch_69fd4f39b5008190b83b3227ce22c509 completed May 8, 2026, 2:49 a.m.
PD Predicate disambiguation batch_69fd4df17c548190a4e2a6fea70f7e10 completed May 8, 2026, 2:44 a.m.
Created at: May 3, 2026, 4:19 p.m.