Triple
T36280013
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NVA operational commands |
E892913
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | functional military command |
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: functional military command Context triple: [NVA operational commands, instanceOf, functional military command]
-
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.
military operational function
A military operational function is a fundamental category of related tasks and capabilities that collectively enable armed forces to plan, conduct, and sustain operations to achieve strategic and tactical objectives.
-
C.
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.
-
D.
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.
-
E.
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.
- 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_69f76e488f34819083e254dbe288c27a |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:09 p.m.