Triple
T33660428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TechnicAtome |
E862335
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | nuclear engineering 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 engineering company Context triple: [TechnicAtome, instanceOf, nuclear engineering 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 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.
-
C.
nuclear engineer
A nuclear engineer is a professional who designs, develops, and manages systems and processes that harness nuclear energy and radiation for applications such as power generation, medicine, and industry while ensuring safety and regulatory compliance.
-
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 power facility
A nuclear power facility is an industrial complex that generates electricity by harnessing heat produced from controlled nuclear fission reactions within reactors, converting it into mechanical and then electrical energy.
- 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_69f34984c4008190bb82f33a7819da64 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:42 a.m.