Triple
T1397965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NED |
E30711
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | nuclear engineering division |
C4335
|
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 division Context triple: [NED, instanceOf, nuclear engineering division]
-
A.
nuclear reactor
A nuclear reactor is a controlled system that initiates, sustains, and regulates a nuclear fission chain reaction to produce heat, typically for generating electricity or powering ships.
-
B.
engineering division
chosen
The engineering division is an organizational unit responsible for designing, developing, and maintaining technical systems, products, and infrastructure within a company or institution.
-
C.
division of a national research institute
A division of a national research institute is a specialized organizational unit responsible for conducting and coordinating research, development, and related activities within a defined scientific or technical domain under the institute’s broader mission.
-
D.
nuclear physicist
A nuclear physicist is a scientist who studies the properties, behavior, and interactions of atomic nuclei and subatomic particles, often to understand fundamental forces and develop applications such as nuclear energy, medical imaging, and radiation technologies.
-
E.
defense contractor division
A defense contractor division is an organizational unit within a defense company responsible for developing, producing, and supporting specific military or security-related products, services, or programs for government and allied clients.
- 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_69a498fd4e408190bd73eca30ea9754c |
completed | March 1, 2026, 7:52 p.m. |
Created at: March 1, 2026, 7:59 p.m.