Triple

T10711626
Position Surface form Disambiguated ID Type / Status
Subject Battle of Savage’s Station E252550 entity
Predicate ConfederateAction P25419 FINISHED
Object pursuit of Union forces 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: pursuit of Union forces | Statement: [Battle of Savage’s Station, ConfederateAction, pursuit of Union forces]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: ConfederateAction
Context triple: [Battle of Savage’s Station, ConfederateAction, pursuit of Union forces]
  • A. commandingConfederateForces
    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.
  • B. ConfederateObjective chosen
    Indicates that an action or plan is aimed at achieving a goal or objective of the Confederate side in a conflict or war.
  • C. effectOnConfederacy
    Indicates the impact or influence that something has on the Confederate side or the Confederacy as a whole.
  • D. combatantConfederate
    Indicates that an entity participates as a combatant on the Confederate side in a conflict or war.
  • E. stateEnteredByConfederates
    Indicates that a particular state or region was entered or invaded by Confederate forces.
  • 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_69d6aa5cbabc8190973e683950d89faf completed April 8, 2026, 7:19 p.m.
NER Named-entity recognition batch_69d6fe523de08190a82c8f057fe8baf6 completed April 9, 2026, 1:18 a.m.
PD Predicate disambiguation batch_69d6f30455888190b77f476b8418eaee completed April 9, 2026, 12:29 a.m.
Created at: April 8, 2026, 9:13 p.m.