Triple
T14074109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Greenbrier Cold War bunker |
E338687
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Cold War facility |
C16080
|
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: Cold War facility Context triple: [The Greenbrier Cold War bunker, instanceOf, Cold War facility]
-
A.
Cold War military site
chosen
A Cold War military site is a strategically located facility, installation, or complex developed or used during the Cold War era for defense, surveillance, weapons deployment, command and control, or related military operations shaped by nuclear deterrence and superpower rivalry.
-
B.
Cold War military infrastructure
Cold War military infrastructure encompasses the global network of bases, missile silos, radar stations, command bunkers, communication systems, and logistical facilities built and maintained by rival blocs to support nuclear deterrence, rapid deployment, and continuous surveillance.
-
C.
former military complex
A former military complex is a decommissioned installation once used for defense or armed forces operations, now repurposed, abandoned, or awaiting redevelopment.
-
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.
weapons testing facility
A weapons testing facility is a secure, controlled site where weapons and related systems are developed, evaluated, and tested for performance, safety, and reliability.
- 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_69d81c687b0c819087fd9ed4198403f8 |
completed | April 9, 2026, 9:38 p.m. |
Created at: April 9, 2026, 10:21 p.m.