Triple
T24090451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hasib Hussain |
E596771
|
entity |
| Predicate | plannedAttackWith |
P155043
|
FINISHED |
| Object | Mohammad Sidique Khan |
—
|
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: Mohammad Sidique Khan | Statement: [Hasib Hussain, plannedAttackWith, Mohammad Sidique Khan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedAttackWith Context triple: [Hasib Hussain, plannedAttackWith, Mohammad Sidique Khan]
-
A.
plannedAttack
Indicates that an entity has intentionally prepared and organized an attack against a target.
-
B.
hasPlannedAttackPoint
Indicates that an entity has designated or selected a specific location as the intended site for carrying out an attack.
-
C.
coordinatedAttacksAlsoTargeted
Indicates that in a set of coordinated attacks, the same target was also attacked as part of those coordinated actions.
-
D.
attackType
Indicates the specific method, style, or category of attack used in an aggressive or hostile action between entities.
-
E.
surpriseAttack
Indicates an aggressive action initiated unexpectedly against a target that is unprepared or unaware.
- 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_69e288c4638c81909bacc28a1e3d436b |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1dc2d405881909469aa95901ab87b |
completed | April 29, 2026, 10:23 a.m. |
| PD | Predicate disambiguation | batch_69f17651458c8190bbfd301883e46085 |
completed | April 29, 2026, 3:09 a.m. |
| PDg | Predicate description generation | batch_69f17b58012c81909106b332db399023 |
completed | April 29, 2026, 3:30 a.m. |
Created at: April 17, 2026, 10:51 p.m.