Triple
T20136335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Locomotive Chase |
E491034
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | American Civil War military raid |
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: American Civil War military raid Context triple: [Great Locomotive Chase, instanceOf, American Civil War military raid]
-
A.
pro-slavery raid
A pro-slavery raid is a violent, organized incursion carried out to capture, intimidate, or suppress individuals or communities in order to defend, expand, or enforce the institution of slavery.
-
B.
United States Army expedition
A United States Army expedition is a formally organized, often temporary military operation conducted by the U.S. Army beyond its usual garrison locations to achieve specific strategic, tactical, or exploratory objectives.
-
C.
antebellum United States incident
An antebellum United States incident is a discrete event or occurrence that took place in the U.S. between the late 18th century and the outbreak of the Civil War in 1861, often reflecting the era’s social, political, or sectional tensions.
-
D.
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.
-
E.
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.
- 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_69da62651a0c8190a3e05e95e056a66b |
completed | April 11, 2026, 3:01 p.m. |
Created at: April 11, 2026, 11:32 p.m.