Triple
T25013267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cold War military installations |
E626054
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military infrastructure category |
C1086
|
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: military infrastructure category Context triple: [Cold War military installations, instanceOf, military infrastructure category]
-
A.
military installation
chosen
A military installation is a designated facility or area where armed forces are stationed, trained, equipped, and supported to conduct defense and security operations.
-
B.
military establishment
A military establishment is an organized institution or network of institutions responsible for a nation's armed forces, defense policies, and related political, economic, and social interests.
-
C.
military-security structure
A military-security structure is an organized system of forces, institutions, and mechanisms designed to protect a state or entity from external and internal threats through defense, intelligence, and enforcement capabilities.
-
D.
military architecture
Military architecture is the specialized design and construction of fortifications, defensive structures, and related military facilities intended to protect territories, control strategic points, and withstand or conduct armed attacks.
-
E.
military training infrastructure network
A military training infrastructure network is an integrated system of facilities, ranges, technologies, and support services designed to plan, deliver, and sustain training activities for armed forces across multiple locations.
- 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_69e2ff27755881908490178e83701160 |
completed | April 18, 2026, 3:48 a.m. |
Created at: April 18, 2026, 6:06 a.m.