Triple
T21064431
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iran–Israel proxy conflict |
E518929
|
entity |
| Predicate | IsraelActionsInclude |
P59465
|
FINISHED |
| Object | airstrikes in Syria |
—
|
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: airstrikes in Syria | Statement: [Iran–Israel proxy conflict, IsraelActionsInclude, airstrikes in Syria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: IsraelActionsInclude Context triple: [Iran–Israel proxy conflict, IsraelActionsInclude, airstrikes in Syria]
-
A.
involvedAction
chosen
Indicates that an entity participates in, performs, or is otherwise engaged in a specified action or activity.
-
B.
includesQuickAction
Indicates that one entity contains or provides an embedded quick action that can be performed directly within it.
-
C.
actsOn
Indicates that one entity performs an action that affects, targets, or is directed toward another entity.
-
D.
SovietAction
Indicates actions, policies, or interventions carried out by the Soviet Union or its authorities toward another entity.
-
E.
isAmerican
Indicates that an entity has American nationality or is from the United States.
- 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_69e0b505ef108190b25dd4033e2ff7eb |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6feb29e388190a80fa969a4daa606 |
completed | April 21, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf9d71881908cd85dfc37db93ca |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:44 p.m.