Triple
T34451802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Magnox Ltd |
E884388
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | nuclear decommissioning company |
C14601
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: nuclear decommissioning company Context triple: [Magnox Ltd, instanceOf, nuclear decommissioning company]
-
A.
nuclear industry company
chosen
A nuclear industry company is an organization that designs, builds, operates, or services nuclear facilities and technologies for energy production, research, medicine, or defense while managing strict safety, regulatory, and environmental requirements.
-
B.
nuclear waste management organization
A nuclear waste management organization is an entity responsible for the safe, secure, and long-term handling, transportation, storage, and disposal of radioactive waste in compliance with regulatory and environmental standards.
-
C.
decommissioned nuclear reactor
A decommissioned nuclear reactor is a permanently shut-down nuclear facility that has been defueled, dismantled or secured, and placed under long-term monitoring and waste management to ensure ongoing safety and environmental protection.
-
D.
uranium mining company
A uranium mining company is a business entity that explores for, extracts, processes, and sells uranium ore used primarily as fuel for nuclear power generation.
-
E.
nuclear technology organization
A nuclear technology organization is an entity that researches, develops, regulates, or applies nuclear science and engineering for energy production, medical, industrial, or defense-related purposes.
- F. None of above.
Provenance (1 batch)
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_69f349c607688190b553539d14901a35 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 2 a.m.