Triple
T31952794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bojinka plot |
E815825
|
entity |
| Predicate | plannedAttackType |
P4333
|
FINISHED |
| Object | simultaneous bombings |
—
|
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: simultaneous bombings | Statement: [Bojinka plot, plannedAttackType, simultaneous bombings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedAttackType Context triple: [Bojinka plot, plannedAttackType, simultaneous bombings]
-
A.
plannedAttack
Indicates that an entity has intentionally prepared and organized an attack against a target.
-
B.
plannedAttackWith
Indicates that one entity has prepared or organized an attack using or involving another entity as the means or instrument of that attack.
-
C.
attackType
chosen
Indicates the specific method, style, or category of attack used in an aggressive or hostile action between entities.
-
D.
coordinatedAttackOn
Indicates a relationship where multiple entities plan or carry out a joint, synchronized attack against a common target.
-
E.
attackTargetType
Indicates the type or category of target that an attack is directed against.
- 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_69f348f4ec708190abbb2a7c3ed58844 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7a225a77c81908f8953ccfeb14336 |
completed | May 3, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69f7a06d4f108190bae3ab9ae431d2c7 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 1, 2026, 12:08 a.m.