Triple
T24503148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Price’s Missouri Expedition |
E617991
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Confederate military operation |
C43017
|
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: Confederate military operation Context triple: [Price’s Missouri Expedition, instanceOf, Confederate military operation]
-
A.
American Civil War military raid
chosen
An American Civil War military raid is a swift, targeted incursion by Union or Confederate forces—often cavalry or small detachments—conducted behind enemy lines to disrupt communications, supply lines, infrastructure, or morale without seeking to hold territory.
-
B.
post–Civil War Southern campaign
A post–Civil War Southern campaign is a coordinated political, social, or military effort undertaken in the American South after 1865 to shape Reconstruction outcomes, reassert regional power, or influence national policy and public opinion.
-
C.
Union Army logistics operation
A Union Army logistics operation is the coordinated planning, procurement, transportation, and distribution of supplies, equipment, and personnel to sustain Union forces during the American Civil War.
-
D.
civil war battle
A civil war battle is an armed conflict between organized factions within the same country, typically involving large-scale military engagements over political, territorial, or ideological control.
-
E.
military confederacy
A military confederacy is a loose alliance of semi-independent states or groups that coordinate their armed forces and defense policies for mutual security while retaining significant political autonomy.
- F. None of above.
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_69e2d7f682108190a1a7ca5fd485ee8a |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 18, 2026, 2:23 a.m.