Triple
T28654809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iran nuclear program |
E725300
|
entity |
| Predicate | technologyComponent |
P44323
|
FINISHED |
| Object | uranium enrichment |
—
|
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: uranium enrichment | Statement: [Iran nuclear program, technologyComponent, uranium enrichment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: technologyComponent Context triple: [Iran nuclear program, technologyComponent, uranium enrichment]
-
A.
technologyType
Indicates the specific kind or category of technology associated with an entity or relationship.
-
B.
technologyClass
Indicates the classification or category of technology to which an entity belongs.
-
C.
technologyIncludes
chosen
Indicates that one technology encompasses, contains, or incorporates another technology as part of its components, features, or implementation.
-
D.
technologyName
Indicates the specific name or designation of a technology associated with an entity.
-
E.
technologyNode
Indicates a relationship where an entity is associated with, implemented in, or characterized by a specific technology node or process technology level.
- 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.