Triple
T31242031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Silkwood v. Kerr-McGee Corp. |
E796586
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | nuclear regulation case |
C1313
|
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 regulation case Context triple: [Silkwood v. Kerr-McGee Corp., instanceOf, nuclear regulation case]
-
A.
nuclear energy law
chosen
Nuclear energy law is the body of legal rules, regulations, and international agreements that govern the safe, secure, and peaceful use, regulation, and oversight of nuclear materials, facilities, and activities.
-
B.
nuclear energy event
A nuclear energy event is an occurrence or process in which energy is released, transformed, or managed through nuclear reactions or radioactive decay, often involving reactors, fuel cycles, or radiation-emitting incidents.
-
C.
Nuclear Regulatory Commission regional office
A Nuclear Regulatory Commission regional office is a decentralized branch of the NRC responsible for overseeing, inspecting, and enforcing nuclear safety and regulatory compliance within a specific geographic area.
-
D.
NRC operating license
An NRC operating license is a formal authorization issued by the U.S. Nuclear Regulatory Commission permitting a facility or entity to operate a nuclear reactor or related nuclear activity under specified safety, security, and regulatory conditions.
-
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_69f224db69ac81909a370adad6a7ac7c |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 9:11 p.m.