Triple
T11131619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of White Bird Canyon |
E263296
|
entity |
| Predicate | NezPerceCasualtiesWounded |
P45724
|
FINISHED |
| Object | few |
—
|
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: few | Statement: [Battle of White Bird Canyon, NezPerceCasualtiesWounded, few]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: NezPerceCasualtiesWounded Context triple: [Battle of White Bird Canyon, NezPerceCasualtiesWounded, few]
-
A.
NativeAmerican casualties
chosen
Indicates the number of Native Americans who were killed, wounded, or otherwise harmed in a specific conflict or violent event.
-
B.
UScasualties
Indicates the number or occurrence of casualties suffered by the United States in a given conflict, event, or situation.
-
C.
wasWoundedIn
Indicates that an entity sustained an injury as a result of a specified event, situation, or conflict.
-
D.
UnionKilledAndWounded
Indicates that members of the Union side in a conflict caused deaths and injuries to others.
-
E.
casualtiesWoundedUS
Indicates that the relationship specifies the number of U.S. individuals who were wounded as casualties in an event or incident.
- 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_69d6aa9c0ba08190bbd19c217489b755 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e831f4808190afabdaa0e97bbe32 |
completed | April 9, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69d75ce104908190b6cc31ef2f67846a |
completed | April 9, 2026, 8:01 a.m. |
Created at: April 8, 2026, 9:28 p.m.