Triple
T29720474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shooting of Amadou Diallo |
E752043
|
entity |
| Predicate | triggeringAction |
P134741
|
FINISHED |
| Object | officers mistook a wallet for a gun |
—
|
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: officers mistook a wallet for a gun | Statement: [Shooting of Amadou Diallo, triggeringAction, officers mistook a wallet for a gun]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: triggeringAction Context triple: [Shooting of Amadou Diallo, triggeringAction, officers mistook a wallet for a gun]
-
A.
triggered
Indicates that one entity causes an event, action, or process involving another entity to start or occur.
-
B.
promptedAction
chosen
Indicates that one entity initiates or triggers another entity to perform a specific action.
-
C.
triggeredFrom
Indicates that one event, action, or process was initiated or caused as a result of another specific event, action, or process.
-
D.
trigger
Indicates that one entity causes or initiates an event, state, or action in another entity or system.
-
E.
executionTrigger
Indicates that one event, condition, or action initiates or causes the execution of another process or operation.
- 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_69f0d628c00c8190ab5ee7e423d7ec3c |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f672fa276881908992aa8271ec91be |
completed | May 2, 2026, 9:56 p.m. |
| PD | Predicate disambiguation | batch_69f66ec5bf508190ad088b89455252bd |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 28, 2026, 7:36 p.m.