Triple
T29712842
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Army operational commands |
E751829
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | operational-level military organization |
C298
|
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-level military organization Context triple: [Army operational commands, instanceOf, operational-level military organization]
-
A.
military organization
chosen
A military organization is a structured group of armed forces personnel and resources, organized under a defined hierarchy and command system, to plan, coordinate, and conduct defense and combat operations in support of a state’s strategic objectives.
-
B.
regional military unit
A regional military unit is an organized group of armed forces assigned to operate within a specific geographic area, responsible for defense, security, and military operations in that region.
-
C.
Operational formation
Operational formation is the structured arrangement and coordination of personnel, resources, and processes designed to execute specific tasks or missions efficiently within an operational context.
-
D.
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.
-
E.
operational unit
An operational unit is an organized group, department, or component within a larger system that performs specific tasks or functions to achieve defined operational objectives.
- 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_69f0d62748848190b030d0a703629a7d |
completed | April 28, 2026, 3:45 p.m. |
Created at: April 28, 2026, 7:32 p.m.