Triple
T28027269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | al-Askari Shrine |
E708157
|
entity |
| Predicate | perpetratorOf2006Attack |
P73120
|
FINISHED |
| Object | suspected al-Qaeda in Iraq |
—
|
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: suspected al-Qaeda in Iraq | Statement: [al-Askari Shrine, perpetratorOf2006Attack, suspected al-Qaeda in Iraq]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: perpetratorOf2006Attack Context triple: [al-Askari Shrine, perpetratorOf2006Attack, suspected al-Qaeda in Iraq]
-
A.
perpetratedAttackOn
Indicates that one entity carried out, organized, or was responsible for an attack directed against another entity.
-
B.
bombingPerpetrator
chosen
Indicates that an entity is responsible for carrying out or organizing a bombing attack against another entity or target.
-
C.
attackedIn
Indicates that one entity carried out an attack in the location, context, or time frame specified by another entity or value.
-
D.
assaultLedBy
Indicates that an assault was directed or coordinated by a particular person or group.
-
E.
killedInAttack
Indicates that an entity died as a direct result of a specific attack event.
- 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_69ef9b6bdd9c8190bb3a574a03774ad1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f63fd79e4c8190af9263b679e5ff07 |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6a8474819091b8c6fe98e3862d |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 8:13 p.m.