Triple
T23400921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2005 Amman bombings in Jordan |
E559501
|
entity |
| Predicate | suicideBombersInvolved |
P70967
|
FINISHED |
| Object | multiple |
—
|
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: multiple | Statement: [2005 Amman bombings in Jordan, suicideBombersInvolved, multiple]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: suicideBombersInvolved Context triple: [2005 Amman bombings in Jordan, suicideBombersInvolved, multiple]
-
A.
numberOfSuicideBombers
chosen
Indicates the quantity of individuals who carry out or are intended to carry out suicide bombing attacks.
-
B.
numberOfPeopleKilledInBombing
Indicates the total count of people who were killed as a direct result of a specific bombing event.
-
C.
numberOfPeopleInjuredInBombings
Indicates the count of individuals who were injured as a result of bombing incidents.
-
D.
bombingPerpetrator
Indicates that an entity is responsible for carrying out or organizing a bombing attack against another entity or target.
-
E.
resultOfBombing
Indicates that something exists or occurs as a consequence or outcome of a bombing 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_69e24549610c8190a069d6411ce5f661 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1a4dfa4c881908df0eced4855c0d9 |
completed | April 29, 2026, 6:27 a.m. |
| PD | Predicate disambiguation | batch_69f061ed34288190a2e5e8cae03b0095 |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:37 p.m.