Triple
T34671233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GOU |
E890383
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | operational command body |
C60832
|
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: operational command body Context triple: [GOU, instanceOf, operational command body]
-
A.
military operational command
chosen
A military operational command is an organizational entity responsible for planning, directing, coordinating, and controlling military forces and resources to achieve specific operational objectives within a defined area or mission scope.
-
B.
operational command role
An operational command role is a position responsible for directing, coordinating, and controlling resources and activities to achieve specific mission objectives within an operational environment.
-
C.
military decision-making body
A military decision-making body is an organized group of authorized personnel responsible for analyzing strategic and tactical information, evaluating options, and issuing binding directives that guide military operations and policy.
-
D.
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.
-
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_69f349d9c59481908b36baa0be093aea |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 2:05 a.m.