Triple
T16559470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Bud Dajo |
E402296
|
entity |
| Predicate | estimatedUSWounded |
P824
|
FINISHED |
| Object | about 50 |
—
|
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 50 | Statement: [Battle of Bud Dajo, estimatedUSWounded, about 50]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: estimatedUSWounded Context triple: [Battle of Bud Dajo, estimatedUSWounded, about 50]
-
A.
casualtiesWoundedUS
chosen
Indicates that the relationship specifies the number of U.S. individuals who were wounded as casualties in an event or incident.
-
B.
hasApproximateNumberOfWounds
Indicates that an entity has a number of wounds that is known only approximately rather than as an exact count.
-
C.
woundedAt
Indicates that an entity was injured or harmed at a specific place or during a particular event.
-
D.
wasWoundedIn
Indicates that an entity sustained an injury as a result of a specified event, situation, or conflict.
-
E.
casualtiesEstimate
Indicates an estimated number of people killed, injured, or otherwise harmed as a result of 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_69d8838648088190acf97ef11fc3f61b |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3576cceb881908579b56d91b15dec |
completed | April 18, 2026, 10:05 a.m. |
| PD | Predicate disambiguation | batch_69e296a47b7481909d9958158510c806 |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:15 a.m.