Triple
T28654766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iran nuclear program |
E725300
|
entity |
| Predicate | initiatedUnderProgram |
P172818
|
FINISHED |
| Object | Atoms for Peace |
—
|
NE NERFINISHED |
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: Atoms for Peace | Statement: [Iran nuclear program, initiatedUnderProgram, Atoms for Peace]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: initiatedUnderProgram Context triple: [Iran nuclear program, initiatedUnderProgram, Atoms for Peace]
-
A.
authorizedUnderProgram
Indicates that an entity’s action, status, or participation is permitted or governed according to the rules or provisions of a specific program.
-
B.
administeredUnderProgram
Indicates that an action or service is carried out within, and governed by the rules or structure of, a specific program.
-
C.
subjectToProgram
Indicates that an entity is governed, regulated, or affected by a specific program, policy, or systematic initiative.
-
D.
regulatesUnderProgram
Indicates that one entity exercises regulatory authority or control over another entity within the scope of a specific program or regulatory scheme.
-
E.
establishedForProgram
Indicates that something has been created or set up specifically to support, serve, or be used by a particular program.
- F. None of above. chosen
Provenance (4 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_69f6b0d21dd08190a9883ff71c94c71c |
completed | May 3, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69f6aca204148190850a3dc325bc07b7 |
completed | May 3, 2026, 2:02 a.m. |
| PDg | Predicate description generation | batch_69f6afeaaef88190aefa97e83f8db906 |
completed | May 3, 2026, 2:16 a.m. |
Created at: April 28, 2026, 4:54 a.m.