Triple
T27172688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1996 Khobar Towers bombing |
E682961
|
entity |
| Predicate | victimNationalityMajority |
P162339
|
FINISHED |
| Object | American |
—
|
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: American | Statement: [1996 Khobar Towers bombing, victimNationalityMajority, American]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: victimNationalityMajority Context triple: [1996 Khobar Towers bombing, victimNationalityMajority, American]
-
A.
hasVictimNationalities
Indicates that an event, incident, or action involved victims belonging to one or more specified nationalities.
-
B.
victimPoliticalStatus
Indicates that the victim holds or is associated with a particular political role, affiliation, or status in relation to the event or action.
-
C.
casualtiesNationalityMajority
chosen
Indicates that the majority of casualties in an incident or event belong to a specified nationality.
-
D.
notableVictimNationality
Indicates that the relationship specifies the nationality of a notable victim associated with an event, incident, or action.
-
E.
victimGroup
Indicates that one group or entity is the target or recipient of harm, abuse, or wrongdoing caused by another.
- 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_69eefad086808190ab89816c0c300476 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f65876c52c8190bc889c7a67bd07f3 |
completed | May 2, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69f6575d89788190aca478e4aea05a65 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 27, 2026, 9:24 a.m.