Triple
T4827213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Office of Naval Reactors |
E107854
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | nuclear regulatory body |
C2929
|
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 regulatory body Context triple: [Office of Naval Reactors, instanceOf, nuclear regulatory body]
-
A.
regulatory authority
A regulatory authority is an official body empowered by law to create, implement, and enforce rules and standards within a specific domain to protect public interests and ensure compliance.
-
B.
nuclear industry company
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.
-
C.
state regulatory agency
chosen
A state regulatory agency is a government body at the state level responsible for creating, implementing, and enforcing rules and standards within specific sectors (such as utilities, health, or finance) to protect the public interest and ensure legal compliance.
-
D.
nuclear weapons lifecycle management organization
An organization responsible for overseeing the planning, development, production, deployment, maintenance, security, modernization, and eventual dismantlement and disposal of nuclear weapons throughout their entire lifecycle.
-
E.
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.
- 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_69bd43fac8188190803f0327190621e4 |
completed | March 20, 2026, 12:56 p.m. |
Created at: March 20, 2026, 1:24 p.m.