Triple
T4799985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kansas City National Security Campus |
E106808
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | national security facility |
C14870
|
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: national security facility Context triple: [Kansas City National Security Campus, instanceOf, national security facility]
-
A.
national security infrastructure
National security infrastructure is the integrated system of physical facilities, technologies, organizations, and legal frameworks designed to protect a nation’s sovereignty, critical assets, and population from internal and external threats.
-
B.
national security system
A national security system is an integrated framework of institutions, policies, technologies, and processes designed to protect a nation’s sovereignty, citizens, critical infrastructure, and interests from internal and external threats.
-
C.
intelligence agency facility
chosen
An intelligence agency facility is a secure, specialized complex where classified information is collected, analyzed, stored, and operations are coordinated to support national security and intelligence objectives.
-
D.
secure facility
A secure facility is a controlled-access location designed with physical, technical, and procedural safeguards to protect people, assets, and sensitive information from unauthorized access or harm.
-
E.
national security function
A national security function is an organized governmental activity or capability dedicated to protecting a nation’s sovereignty, people, infrastructure, and interests from internal and external threats.
- 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_69bd43f6a1e08190bf0a372bfc336ee5 |
completed | March 20, 2026, 12:56 p.m. |
Created at: March 20, 2026, 1:23 p.m.