Triple
T28654806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iran nuclear program |
E725300
|
entity |
| Predicate | JCPOAEffect |
P22778
|
FINISHED |
| Object | sanctions relief for Iran |
—
|
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: sanctions relief for Iran | Statement: [Iran nuclear program, JCPOAEffect, sanctions relief for Iran]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: JCPOAEffect Context triple: [Iran nuclear program, JCPOAEffect, sanctions relief for Iran]
-
A.
JCPOAParticipant
Indicates that an entity takes part in, is a signatory to, or is otherwise formally involved in the Joint Comprehensive Plan of Action (JCPOA).
-
B.
impactOnIran
chosen
Indicates the effect or consequences that an action, event, or policy has on Iran.
-
C.
treatyEffect
Indicates that a treaty produces a specific legal, political, or practical consequence or change in the relationship between the involved parties.
-
D.
nuclearCooperationIncludes
Indicates that a nuclear cooperation agreement or relationship encompasses, contains, or covers a specified component, activity, or aspect.
-
E.
tookEffect
Indicates that a change, rule, condition, or event became active, operative, or started producing its intended consequences.
- 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_69f01d84f5f0819087ab5e6143b14ed7 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c2198208190a3954086c22cfcbf |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 4:54 a.m.