Triple
T557418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rules for Construction of Nuclear Facility Components |
E11972
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | nuclear industry standard |
C2538
|
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 industry standard Context triple: [Rules for Construction of Nuclear Facility Components, instanceOf, nuclear industry standard]
-
A.
nuclear energy law
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 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.
-
C.
IEEE standard
An IEEE standard is a formally documented set of technical specifications and guidelines developed and maintained by the Institute of Electrical and Electronics Engineers to ensure interoperability, safety, and quality across electrical, electronic, and computing technologies.
-
D.
military standard
A military standard is an officially established set of technical, procedural, or quality requirements used by armed forces to ensure compatibility, reliability, and uniformity of equipment, systems, and practices.
-
E.
engineering standard
chosen
An engineering standard is a documented set of agreed-upon technical criteria, methods, and requirements intended to ensure safety, interoperability, quality, and consistency in engineering design, production, and operation.
- 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_69a4932941d08190815efd422f0b4ca7 |
completed | March 1, 2026, 7:27 p.m. |
Created at: March 1, 2026, 7:32 p.m.