Triple
T23796937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States Embassy in Beirut |
E588565
|
entity |
| Predicate | wasAttackedOn |
P35766
|
FINISHED |
| Object | 1983-04-18 |
—
|
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: 1983-04-18 | Statement: [United States Embassy in Beirut, wasAttackedOn, 1983-04-18]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasAttackedOn Context triple: [United States Embassy in Beirut, wasAttackedOn, 1983-04-18]
-
A.
attackedIn
Indicates that one entity carried out an attack in the location, context, or time frame specified by another entity or value.
-
B.
countryAttacked
Indicates that one country has carried out an attack against another country.
-
C.
wasAttackedInYear
chosen
Indicates that an entity was the target of an attack that occurred in the specified year.
-
D.
cityAttackedBy
Indicates that a city is the target of an attack carried out by a specified agent or force.
-
E.
wasInvadedBy
Indicates that a place or territory was subjected to an incursion or attack carried out by another entity or group.
- 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_69e25d15db58819092ac1e6791696fd9 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c6ddc2d88190b6124d9fb2695d24 |
completed | April 29, 2026, 8:52 a.m. |
| PD | Predicate disambiguation | batch_69f155fe300481909bd617443228df65 |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:50 p.m.