Triple
T28654787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iran nuclear program |
E725300
|
entity |
| Predicate | viewedAsRiskBy |
P165534
|
FINISHED |
| Object | United States |
—
|
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: United States | Statement: [Iran nuclear program, viewedAsRiskBy, United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: viewedAsRiskBy Context triple: [Iran nuclear program, viewedAsRiskBy, United States]
-
A.
hasRiskFrom
Indicates that one entity is exposed to or may suffer potential harm, loss, or adverse effects as a result of another entity.
-
B.
riskListedBy
Indicates that a risk has been documented, identified, or cataloged by a particular agent or source.
-
C.
hasRiskStatus
Indicates the level or category of risk currently associated with an entity.
-
D.
riskDepicted
Indicates that a representation (such as an image, text, or symbol) portrays, illustrates, or conveys the presence or possibility of a particular risk.
-
E.
focusesOnRisk
Indicates that the subject directs attention, resources, or analysis primarily toward identifying, assessing, or managing risk.
- 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_69f6596b210481908af6cd555748f75b |
completed | May 2, 2026, 8:07 p.m. |
| PD | Predicate disambiguation | batch_69f65760fd3081908ffe014a5e2bf069 |
completed | May 2, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f658ebeca4819096beb3f98f73fe31 |
completed | May 2, 2026, 8:05 p.m. |
Created at: April 28, 2026, 4:54 a.m.