Triple
T6224564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Appomattox Station and Appomattox Court House operations |
E139197
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Union victory |
C19440
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Union victory Context triple: [Appomattox Station and Appomattox Court House operations, instanceOf, Union victory]
-
A.
Confederate victory
A Confederate victory is a historical outcome in which the Confederate States of America successfully won a specific military engagement, campaign, or strategic objective during the American Civil War.
-
B.
Union offensive
Union offensive refers to the coordinated series of military campaigns and strategic initiatives launched by the Union during the American Civil War to weaken, divide, and ultimately defeat the Confederacy.
-
C.
union republic
A union republic is a constituent political unit within a federal or quasi-federal state, typically possessing its own government and constitution while remaining subordinate to the overarching union authority.
-
D.
unionism
Unionism is the advocacy and practice of organizing workers into unions to collectively negotiate for better wages, conditions, and rights, or, in a political context, the support for maintaining or forming a political union between regions or states.
-
E.
year of military victories
A year of military victories represents a specific calendar year characterized by a notable concentration of successful military engagements or campaigns achieved by a particular state, alliance, or armed force.
- F. None of above. chosen
Provenance (1 batch)
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_69c008afd3148190b71e9eaa60420dd1 |
completed | March 22, 2026, 3:20 p.m. |
Created at: March 22, 2026, 4:22 p.m.