Triple
T24862765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baxter Springs Massacre |
E622196
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | American Civil War massacre |
C637
|
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 massacre Context triple: [Baxter Springs Massacre, instanceOf, American Civil War massacre]
-
A.
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.
-
B.
massacre
chosen
A massacre is the deliberate and brutal killing of a large number of defenseless or unresisting people or animals, often carried out in a single event or short period of time.
-
C.
American Civil War military raid
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.
-
D.
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.
-
E.
event in Bleeding Kansas
An event in Bleeding Kansas is a specific historical incident of political conflict or violent confrontation between pro-slavery and anti-slavery forces in the Kansas Territory during the mid-1850s.
- 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_69e2fac350d08190b3affde1b451a8c5 |
completed | April 18, 2026, 3:30 a.m. |
Created at: April 18, 2026, 5:22 a.m.