Triple
T29720466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shooting of Amadou Diallo |
E752043
|
entity |
| Predicate | victimArmedStatus |
P169689
|
FINISHED |
| Object | unarmed |
—
|
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: unarmed | Statement: [Shooting of Amadou Diallo, victimArmedStatus, unarmed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: victimArmedStatus Context triple: [Shooting of Amadou Diallo, victimArmedStatus, unarmed]
-
A.
victimStatus
Indicates the condition or state of a person who has been harmed or wronged as a result of an event, action, or offense.
-
B.
isVictimOf
Indicates that one entity suffers harm, loss, or wrongdoing as a result of another entity’s actions or events.
-
C.
victimState
Indicates the condition or status that a victim is in as a result of an event, action, or harmful incident.
-
D.
victimRole
Indicates that one entity participates in an event or situation specifically in the role of the victim or harmed party.
-
E.
victimSide
Indicates that one entity is on, represents, or corresponds to the side of the victim in a conflict, incident, or harmful event.
- F. None of above. chosen
Provenance (4 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_69f0d628c00c8190ab5ee7e423d7ec3c |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f68048391c8190abe6580678f8a9ef |
completed | May 2, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69f67e40af9881908de3a4aa15f70a83 |
completed | May 2, 2026, 10:44 p.m. |
| PDg | Predicate description generation | batch_69f67f7e116c819099aec724e9ef3763 |
completed | May 2, 2026, 10:49 p.m. |
Created at: April 28, 2026, 7:36 p.m.