Triple
T32091232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2019 Pulwama attack |
E819597
|
entity |
| Predicate | suicideBomber |
P73120
|
FINISHED |
| Object | Adil Ahmad Dar |
—
|
NE NERFINISHED |
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: Adil Ahmad Dar | Statement: [2019 Pulwama attack, suicideBomber, Adil Ahmad Dar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: suicideBomber Context triple: [2019 Pulwama attack, suicideBomber, Adil Ahmad Dar]
-
A.
numberOfSuicideBombers
Indicates the quantity of individuals who carry out or are intended to carry out suicide bombing attacks.
-
B.
bombingPerpetrator
chosen
Indicates that an entity is responsible for carrying out or organizing a bombing attack against another entity or target.
-
C.
designedToBomb
Indicates that something was intentionally created or configured for the purpose of bombing a target.
-
D.
perpetratorOfKilling
Indicates that an entity is the one who carried out or caused a particular killing.
-
E.
bombType
Indicates the specific kind or category of bomb associated with an event, object, or action.
- 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_69f349004b2481908ce2e50af0d579a8 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b63db9dc81908861caf2a676a5d9 |
completed | May 3, 2026, 2:43 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a7bdb481908d16a32f49e38c2c |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:25 a.m.