Triple
T32037174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NRC Reactor Oversight Process |
E818126
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regulatory oversight framework |
C11529
|
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: regulatory oversight framework Context triple: [NRC Reactor Oversight Process, instanceOf, regulatory oversight framework]
-
A.
regulatory framework
chosen
A regulatory framework is a structured set of rules, guidelines, and enforcement mechanisms established by authorities to govern behaviors, processes, and standards within a specific domain.
-
B.
administrative oversight regime
An administrative oversight regime is a structured system of rules, procedures, and institutions designed to monitor, review, and correct the actions and decisions of administrative bodies to ensure legality, accountability, and fairness.
-
C.
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.
-
D.
federal oversight body
A federal oversight body is a government entity responsible for monitoring, evaluating, and enforcing compliance with laws, regulations, and standards across federal agencies or sectors to ensure accountability and integrity.
-
E.
legislative oversight mechanism
A legislative oversight mechanism is a structured process or tool through which a legislative body monitors, reviews, and influences the actions and decisions of the executive branch or public agencies to ensure accountability, legality, and alignment with policy goals.
- 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_69f348fbc8148190b3c0f95d4772b153 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:19 a.m.