Triple
T23529411
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1984 United States embassy annex bombing in Beirut |
E576521
|
entity |
| Predicate | killedAmericans |
P823
|
FINISHED |
| Object | 2 |
—
|
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: 2 | Statement: [1984 United States embassy annex bombing in Beirut, killedAmericans, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: killedAmericans Context triple: [1984 United States embassy annex bombing in Beirut, killedAmericans, 2]
-
A.
casualtiesKilledUS
chosen
Indicates that the relationship specifies the number of U.S. individuals who were killed as casualties in an event or incident.
-
B.
UScasualties
Indicates the number or occurrence of casualties suffered by the United States in a given conflict, event, or situation.
-
C.
numberOfVictimsKilled
Indicates the count of victims who were killed as a result of the referenced event or action.
-
D.
sonsKilledBy
Indicates that the referenced sons are those who were killed by the specified agent or entity.
-
E.
governmentCasualties
Indicates that members of a government (such as officials, employees, or security forces) were killed, injured, or otherwise became casualties in an event or conflict.
- 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_69e245f5a8848190a2ba42e271c6c31f |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1ac7646a48190b5dcbaf8c0c194df |
completed | April 29, 2026, 7 a.m. |
| PD | Predicate disambiguation | batch_69f1189d75b48190a1c01928a993c9fb |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:09 p.m.