Triple
T21970803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | mobile White House |
E542582
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | secure communications facility |
C11563
|
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: secure communications facility Context triple: [mobile White House, instanceOf, secure communications facility]
-
A.
secure facility
chosen
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.
-
B.
secure storage facility
A secure storage facility is a highly protected, access-controlled environment designed to safely store valuable, sensitive, or hazardous items against theft, damage, and unauthorized access.
-
C.
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.
-
D.
security service network
A security service network is an interconnected system of tools, protocols, and infrastructure designed to monitor, protect, and manage the security of digital assets and communications across distributed environments.
-
E.
security mechanism
A security mechanism is a method, process, or tool designed to protect systems, data, or communications from unauthorized access, misuse, or harm.
- 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_69e0c48070988190909db97667b9a0ac |
completed | April 16, 2026, 11:14 a.m. |
Created at: April 16, 2026, 8:02 p.m.