Triple
T28715140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dade’s Massacre |
E729939
|
entity |
| Predicate | Seminole_casualties |
P47610
|
FINISHED |
| Object | minimal |
—
|
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: minimal | Statement: [Dade’s Massacre, Seminole_casualties, minimal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Seminole_casualties Context triple: [Dade’s Massacre, Seminole_casualties, minimal]
-
A.
NativeAmerican casualties
Indicates the number of Native Americans who were killed, wounded, or otherwise harmed in a specific conflict or violent event.
-
B.
confederateCasualtiesAndLosses
Indicates the number or extent of casualties and material losses suffered by Confederate forces in a conflict or engagement.
-
C.
casualtiesTexianKilled
Indicates that the relationship specifies the number of Texian individuals who were killed as casualties in a particular event or conflict.
-
D.
insurgentCasualties
Indicates the number of insurgents who were killed, wounded, or otherwise rendered casualties in a given event or context.
-
E.
nativeCasualties
chosen
Indicates that native or indigenous people suffered deaths or injuries as a result of a particular event, action, or conflict.
- 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_69f043e7d5a4819094b18aca10b1e024 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f658ee40088190b71e1219407690d0 |
completed | May 2, 2026, 8:05 p.m. |
| PD | Predicate disambiguation | batch_69f65760fd3081908ffe014a5e2bf069 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 5:50 a.m.