Triple
T22821247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TRUPACT-II shipping casks |
E565234
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | engineered containment system |
C41751
|
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: engineered containment system Context triple: [TRUPACT-II shipping casks, instanceOf, engineered containment system]
-
A.
engineered system
chosen
An engineered system is a deliberately designed and organized set of interacting components, processes, and resources created by humans to perform specific functions and achieve defined objectives within given constraints.
-
B.
radiation containment structure
A radiation containment structure is a protective enclosure designed to prevent the escape of harmful ionizing radiation from sources such as nuclear reactors, medical equipment, or radioactive materials into the surrounding environment.
-
C.
small self-contained experiment container
A small self-contained experiment container is a compact, isolated environment that bundles all necessary code, data, and dependencies to run and reproduce a specific experiment independently of external systems.
-
D.
command-and-control facility
A command-and-control facility is a secure, centralized location equipped with communication, monitoring, and decision-support systems used to direct and coordinate operations and resources in real time.
-
E.
enclave
An enclave is a distinct, self-contained area or community that is geographically, culturally, or functionally separated from its surrounding environment while remaining embedded within it.
- 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_69e2458426188190b58b8ab4844fe420 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 17, 2026, 3:33 p.m.