Triple
T28715101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dade’s Battle |
E729938
|
entity |
| Predicate | SeminoleCasualtiesKilled |
P45724
|
FINISHED |
| Object | relatively light |
—
|
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: relatively light | Statement: [Dade’s Battle, SeminoleCasualtiesKilled, relatively light]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: SeminoleCasualtiesKilled Context triple: [Dade’s Battle, SeminoleCasualtiesKilled, relatively light]
-
A.
casualtiesTexianKilled
Indicates that the relationship specifies the number of Texian individuals who were killed as casualties in a particular event or conflict.
-
B.
NativeAmerican casualties
chosen
Indicates the number of Native Americans who were killed, wounded, or otherwise harmed in a specific conflict or violent event.
-
C.
CubanCasualtiesKilled
Indicates that Cuban individuals were killed as casualties in a specific event or conflict.
-
D.
casualtiesKilledUS
Indicates that the relationship specifies the number of U.S. individuals who were killed as casualties in an event or incident.
-
E.
numberOfVictimsKilled
Indicates the count of victims who were killed as a result of the referenced event or action.
- 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_69f656da9f18819092fc744f5145a26b |
completed | May 2, 2026, 7:56 p.m. |
| PD | Predicate disambiguation | batch_69f651ac855481908e30c3b345d31356 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 5:50 a.m.