Triple
T32091234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2019 Pulwama attack |
E819597
|
entity |
| Predicate | suicideBomberOrigin |
P174126
|
FINISHED |
| Object | Kashmir |
—
|
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: Kashmir | Statement: [2019 Pulwama attack, suicideBomberOrigin, Kashmir]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: suicideBomberOrigin Context triple: [2019 Pulwama attack, suicideBomberOrigin, Kashmir]
-
A.
bombingPerpetrator
Indicates that an entity is responsible for carrying out or organizing a bombing attack against another entity or target.
-
B.
numberOfSuicideBombers
Indicates the quantity of individuals who carry out or are intended to carry out suicide bombing attacks.
-
C.
bombingName
Indicates that an entity is the name or designated title of a specific bombing event or bombing attack.
-
D.
bombingLocation
Indicates the place where a bombing event occurs or is carried out.
-
E.
detonatedBy
Indicates that an explosive or device is set off or caused to explode by a particular agent or entity.
- 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_69f349004b2481908ce2e50af0d579a8 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bcc425588190afd0dceba43ed79f |
completed | May 3, 2026, 3:11 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6cef208190bc5cd43d96127004 |
completed | May 3, 2026, 3:01 a.m. |
| PDg | Predicate description generation | batch_69f6bbbe23d48190b2aa662d69b41900 |
completed | May 3, 2026, 3:06 a.m. |
Created at: May 1, 2026, 12:25 a.m.