Triple
T29380187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | C-LAS |
E745113
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | army command role |
C35959
|
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: army command role Context triple: [C-LAS, instanceOf, army command role]
-
A.
army commander post
An army commander post is a designated command facility or position from which a military commander directs, coordinates, and controls the operations of assigned forces.
-
B.
United States Army command
The United States Army command is the organizational structure and authority framework responsible for directing, coordinating, and controlling Army forces and operations to accomplish national defense objectives.
-
C.
Soviet military command role
chosen
A Soviet military command role is a position within the hierarchical structure of the Soviet Armed Forces responsible for planning, directing, and controlling military operations in accordance with Communist Party doctrine and centralized state authority.
-
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.
field army–level command
A field army–level command is a large, operational military formation responsible for directing multiple corps or equivalent units within a theater of operations to achieve strategic 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_69f0a79cfd5481909b4dde750cb8d2c6 |
completed | April 28, 2026, 12:27 p.m. |
Created at: April 28, 2026, 2:34 p.m.