Triple
T25307642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | California National Guard armories |
E634523
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military facility network |
C41908
|
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 facility network Context triple: [California National Guard armories, instanceOf, military facility network]
-
A.
military base network
chosen
A military base network is an interconnected system of communication, data, and operational infrastructure linking facilities, units, and resources across one or more military installations to support command, control, logistics, and security functions.
-
B.
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.
-
C.
military installation
A military installation is a designated facility or area where armed forces are stationed, trained, equipped, and supported to conduct defense and security operations.
-
D.
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.
-
E.
Ministry of Defence facility
A Ministry of Defence facility is a secured government-controlled site used for the planning, coordination, support, and execution of national defence and military operations.
- 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_69e75a972c6481909bc11710e8d30a6c |
completed | April 21, 2026, 11:08 a.m. |
Created at: April 21, 2026, 1:25 p.m.