Triple
T36347357
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Outpost 54 Castle Bravo |
E895100
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | containment facility |
C38790
|
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: containment facility Context triple: [Outpost 54 Castle Bravo, instanceOf, containment facility]
-
A.
radiation containment structure
chosen
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.
-
B.
Enclave facility
An Enclave facility is a secure, self-contained installation designed to isolate, protect, and control sensitive operations, resources, or populations from external access or influence.
-
C.
biological weapons research facility
A biological weapons research facility is a secure, specialized laboratory complex where scientists develop, test, and sometimes produce pathogenic agents or toxins intended for use in warfare or hostile activities.
-
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.
torture facility
A torture facility is a controlled environment where individuals are deliberately subjected to severe physical or psychological pain, coercion, or degradation, typically for punishment, intimidation, or extracting information.
- 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_69f76e4f437c8190a1af3ea2564f41f5 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:09 p.m.