Triple
T33401011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iran |
E855296
|
entity |
| Predicate | hasNuclearProgram |
P17998
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Iran, hasNuclearProgram, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNuclearProgram Context triple: [Iran, hasNuclearProgram, yes]
-
A.
hasNuclearWeapons
Indicates that the subject possesses or controls nuclear weapons.
-
B.
hasNuclearRole
Indicates that an entity participates in, is responsible for, or holds authority related to nuclear activities, functions, or capabilities.
-
C.
nuclearWeaponsProgram
chosen
Indicates the existence, development, or pursuit of a program related to the research, production, or maintenance of nuclear weapons.
-
D.
countryNuclearProgram
Indicates that a country possesses, develops, or maintains a nuclear weapons or nuclear energy program.
-
E.
hasNuclearActivity
Indicates that an entity engages in, is involved with, or possesses capabilities related to nuclear activities or operations.
- 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_69f3496e3f1c8190bcecfa82aa9d17ff |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fe6739d4dc8190ae7505c089bbac29 |
completed | May 8, 2026, 10:44 p.m. |
| PD | Predicate disambiguation | batch_69fe6541dffc81909c66a61ba69f38fc |
completed | May 8, 2026, 10:35 p.m. |
Created at: May 1, 2026, 1:35 a.m.