Triple
T31106854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Castle Bravo underwater base |
E792816
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Monarch facility |
C58984
|
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: Monarch facility Context triple: [Castle Bravo underwater base, instanceOf, Monarch facility]
-
A.
royal culinary facility
A royal culinary facility is a specialized kitchen complex within a palace or royal estate where highly trained staff prepare, store, and manage food and beverages for the royal household and official state functions.
-
B.
FEMA facility
A FEMA facility is a government-operated site used by the Federal Emergency Management Agency to coordinate disaster preparedness, response, recovery, and mitigation activities, including housing personnel, equipment, and emergency operations centers.
-
C.
SEAT facility
A SEAT facility is a specialized location equipped to conduct standardized environmental assessment tests, typically focusing on evaluating and monitoring specific ecological, safety, or performance criteria.
-
D.
SAP facility
An SAP facility is a physical or virtual location within an organization where SAP systems, infrastructure, and related operations are hosted, managed, and supported to enable business processes.
-
E.
Thales Group facility
A Thales Group facility is a physical site owned or operated by Thales where research, development, production, testing, or support activities related to its aerospace, defense, security, or transportation solutions are conducted.
- F. None of above. chosen
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_69f224cfd5d881908ec6447bc321cd58 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 9:03 p.m.