Triple
T3076359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of the Wabash |
E64145
|
entity |
| Predicate | U.S. casualties |
P823
|
FINISHED |
| Object | over 600 U.S. soldiers killed |
—
|
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: over 600 U.S. soldiers killed | Statement: [Battle of the Wabash, U.S. casualties, over 600 U.S. soldiers killed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: U.S. casualties Context triple: [Battle of the Wabash, U.S. casualties, over 600 U.S. soldiers killed]
-
A.
casualtiesKilledUS
chosen
Indicates that the relationship specifies the number of U.S. individuals who were killed as casualties in an event or incident.
-
B.
casualtiesUnitedStates
Indicates that the event or situation resulted in casualties (deaths and/or injuries) among United States personnel or citizens.
-
C.
UScasualties
Indicates the number or occurrence of casualties suffered by the United States in a given conflict, event, or situation.
-
D.
casualties
Indicates that an event, action, or situation resulted in people being killed or injured.
-
E.
casualtiesImpact
Indicates how the number or severity of casualties affects or influences another factor, situation, or outcome.
- 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_69ad857a8aec8190bfdfd9c14554ac5a |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada1a5b4108190979654b459990afd |
completed | March 8, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69ad9debb6308190be28378ae1fc98af |
completed | March 8, 2026, 4:03 p.m. |
Created at: March 8, 2026, 3:02 p.m.