Triple
T24862788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baxter Springs Massacre |
E622196
|
entity |
| Predicate | killedConfederate |
P34511
|
FINISHED |
| Object | about 3–10 (estimates vary) |
—
|
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: about 3–10 (estimates vary) | Statement: [Baxter Springs Massacre, killedConfederate, about 3–10 (estimates vary)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: killedConfederate Context triple: [Baxter Springs Massacre, killedConfederate, about 3–10 (estimates vary)]
-
A.
ConfederateOfficerKilled
Indicates that an individual serving as a Confederate officer was killed.
-
B.
killedOrCaptured
Indicates that one entity has either killed or taken another entity into custody or control.
-
C.
killedBy
Indicates that one entity caused the death of another entity.
-
D.
combatantConfederate
Indicates that an entity participates as a combatant on the Confederate side in a conflict or war.
-
E.
confederateCasualtiesAndLosses
chosen
Indicates the number or extent of casualties and material losses suffered by Confederate forces in a conflict or engagement.
- 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_69e2fac350d08190b3affde1b451a8c5 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f453035f508190be83a3d521723acf |
completed | May 1, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f44d6ef33081908f5d36ba1ae5f473 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 5:22 a.m.