Triple
T29696823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Military Planning and Conduct Capability |
E751374
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | strategic-level headquarters |
C400
|
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: strategic-level headquarters Context triple: [Military Planning and Conduct Capability, instanceOf, strategic-level headquarters]
-
A.
headquarters
chosen
The headquarters is the primary location where an organization’s central management, strategic decision-making, and key administrative functions are coordinated and controlled.
-
B.
high-readiness headquarters
A high-readiness headquarters is a command center designed, staffed, and equipped to rapidly assume control of operations, coordinate resources, and make timely decisions in response to emerging crises or missions.
-
C.
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.
-
D.
headquarters and service company
A headquarters and service company is an organizational entity that centralizes strategic management, administrative support, and shared services for multiple business units or subsidiaries.
-
E.
headquarters agreement
A headquarters agreement is a formal treaty or contract between an international organization and a host state that defines the legal status, privileges, immunities, and operational conditions of the organization’s headquarters within that state.
- 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_69f0d6266f8481909e70bb41cda18587 |
completed | April 28, 2026, 3:45 p.m. |
Created at: April 28, 2026, 7:20 p.m.