Triple
T21970802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | mobile White House |
E542582
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | airborne command center |
C18649
|
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: airborne command center Context triple: [mobile White House, instanceOf, airborne command center]
-
A.
airborne command post
chosen
An airborne command post is an aircraft equipped with advanced communications, surveillance, and control systems that enables military or government leaders to direct operations and maintain command and control while in flight.
-
B.
deployable air command and control centre
A deployable air command and control centre is a mobile, rapidly configurable facility that provides the infrastructure, systems, and personnel needed to plan, direct, and coordinate air operations in a given theater.
-
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.
command and control centre
A command and control centre is a centralized facility where information is collected, analyzed, and used to coordinate and direct operations, resources, and decision-making in real time.
-
E.
military aviation command
A military aviation command is an organizational unit responsible for planning, directing, coordinating, and controlling the employment, readiness, and support of air forces to achieve strategic and operational military objectives.
- 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.