Triple
T9386714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UK Strategic Command Headquarters |
E225922
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | joint military command headquarters |
C8007
|
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: joint military command headquarters Context triple: [UK Strategic Command Headquarters, instanceOf, joint military command headquarters]
-
A.
joint command
chosen
A joint command is a unified military authority structure that coordinates and directs operations involving multiple service branches or allied forces to achieve common strategic objectives.
-
B.
deployable corps-level headquarters
A deployable corps-level headquarters is a mobile, command-and-control organization capable of planning, coordinating, and directing large-scale, multi-division military operations across a theater of operations.
-
C.
NATO rapid reaction corps headquarters
The NATO Rapid Reaction Corps Headquarters is a high-readiness, multinational command element responsible for planning, coordinating, and directing rapid deployment and operations of NATO land forces in crisis or conflict.
-
D.
military special operations command
A military special operations command is a specialized organizational unit responsible for planning, directing, and executing high-risk, strategically critical missions using elite, highly trained forces.
-
E.
United States military command
The United States military command is the hierarchical structure of authority and control through which national defense policies and military operations are directed, coordinated, and executed across all branches of the U.S. Armed Forces.
- 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_69ca842e9dcc8190a264119e683cfe04 |
completed | March 30, 2026, 2:09 p.m. |
Created at: March 30, 2026, 7:45 p.m.