Triple
T21624670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Kamdesh |
E533667
|
entity |
| Predicate | casualtiesAfghanForcesKilled |
P40994
|
FINISHED |
| Object | 3 |
—
|
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: 3 | Statement: [Battle of Kamdesh, casualtiesAfghanForcesKilled, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: casualtiesAfghanForcesKilled Context triple: [Battle of Kamdesh, casualtiesAfghanForcesKilled, 3]
-
A.
AfghanCasualties
chosen
Indicates the number or occurrence of casualties suffered by Afghan individuals or forces in a given event or context.
-
B.
alQaedaCasualties
Indicates that the relationship specifies the number or occurrence of casualties suffered by al-Qaeda members or forces in a given event or context.
-
C.
casualtiesIraqiMilitaryKilled
Indicates that the number of casualties refers specifically to Iraqi military personnel who were killed.
-
D.
militaryDeaths
Indicates the number of individuals who died while serving in a military capacity, typically during armed conflict or related operations.
-
E.
militaryUnitInvolvedInDeath
Indicates that a specific military unit participated in, contributed to, or was otherwise involved in causing a particular death.
- 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_69e0c464fba881908d0ff2ac80511ce1 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef52121c3c8190b9b4d862ed247c71 |
completed | April 27, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69e69665fe8c8190af7e38785db188b2 |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:34 p.m.