Triple
T30656992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nidal Ayyad |
E780411
|
entity |
| Predicate | terroristActivity |
P99240
|
FINISHED |
| Object | 1993 World Trade Center bombing |
—
|
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: 1993 World Trade Center bombing | Statement: [Nidal Ayyad, terroristActivity, 1993 World Trade Center bombing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terroristActivity Context triple: [Nidal Ayyad, terroristActivity, 1993 World Trade Center bombing]
-
A.
usedTerrorism
Indicates that an entity employed or supported acts of terrorism as a means to achieve its objectives.
-
B.
typeOfTerrorism
Indicates a classification relationship where an act or event is identified as belonging to a specific category or type of terrorism.
-
C.
terroristOrganization
Indicates that an entity is recognized as a group that plans, supports, or carries out acts of terrorism.
-
D.
positionOnTerrorism
Indicates a stance or viewpoint that an entity holds regarding terrorism, such as its causes, legitimacy, or appropriate responses.
-
E.
terroristRole
chosen
Indicates that an entity plays a specific functional role within a terrorist organization or terrorist activity.
- 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_69f224a6d10481909290be1a00fc83b3 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68ade49d48190a80182cf054bd154 |
completed | May 2, 2026, 11:38 p.m. |
| PD | Predicate disambiguation | batch_69f6861170d08190bb98be609d436f84 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:30 p.m.