Triple
T31013886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AFPSOCOM |
E790276
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | unified military command |
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: unified military command Context triple: [AFPSOCOM, instanceOf, unified military command]
-
A.
central military command
A central military command is the highest-level organizational authority responsible for planning, directing, and coordinating the overall operations and strategy of a nation’s armed forces.
-
B.
military advisory command
A military advisory command is an organizational unit responsible for providing strategic, operational, and technical guidance to allied or subordinate forces to enhance their effectiveness and interoperability.
-
C.
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.
-
D.
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.
-
E.
subordinate unified combatant command
A subordinate unified combatant command is a command established by a unified combatant command to conduct operations on a continuing basis within a specific functional or geographic area under the authority of that parent unified command.
- 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_69f224c73ca48190a1e46cb58ad4045b |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:57 p.m.