Triple
T31952797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bojinka plot |
E815825
|
entity |
| Predicate | conspiracyType |
P173045
|
FINISHED |
| Object | international terrorism |
—
|
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: international terrorism | Statement: [Bojinka plot, conspiracyType, international terrorism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conspiracyType Context triple: [Bojinka plot, conspiracyType, international terrorism]
-
A.
conspiracy
Indicates a secret agreement or collaboration between multiple entities to plan or carry out an unlawful, deceptive, or harmful act.
-
B.
conspiracyLocation
Indicates the place where a conspiracy is planned, organized, or carried out.
-
C.
deathConspiracy
Indicates a relationship where one party is involved in planning, supporting, or believing in a covert plot to cause another party’s death.
-
D.
conspirator
Indicates that an entity participates with others in planning or carrying out a secret or illicit scheme or action.
-
E.
positionOnConspiracy
Indicates the stance or viewpoint an entity holds regarding a particular conspiracy or conspiracy theory.
- 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_69f348f4ec708190abbb2a7c3ed58844 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b2d9aad88190a445f8f591cb19fc |
completed | May 3, 2026, 2:28 a.m. |
| PD | Predicate disambiguation | batch_69f6b151ad008190836c1bcdec503ce2 |
completed | May 3, 2026, 2:22 a.m. |
| PDg | Predicate description generation | batch_69f6b21da77081908c5c015c4606d344 |
completed | May 3, 2026, 2:25 a.m. |
Created at: May 1, 2026, 12:08 a.m.