Triple
T16238459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Combustion Engineering |
E394177
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | nuclear technology 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 technology company Context triple: [Combustion Engineering, instanceOf, nuclear technology 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.
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.
-
C.
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.
-
D.
nuclear weapons component plant
A nuclear weapons component plant is an industrial facility dedicated to designing, manufacturing, and assembling specialized parts and subsystems used in the construction and maintenance of nuclear weapons.
-
E.
multinational utility company
A multinational utility company is a large-scale enterprise that provides essential services such as electricity, gas, water, or telecommunications across multiple countries, operating under diverse regulatory, cultural, and market conditions.
- 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_69d87f2171208190951025e526947816 |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 10, 2026, 5:04 a.m.