Triple
T28386988
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | General Headquarters, U.S. Army (in concept) |
E719044
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | proposed military command |
C50085
|
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: proposed military command Context triple: [General Headquarters, U.S. Army (in concept), instanceOf, proposed military command]
-
A.
planned military formation
chosen
A planned military formation is a deliberately organized arrangement of troops, vehicles, or units in space and time designed to achieve specific tactical or strategic objectives under anticipated conditions.
-
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.
Soviet military command role
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.
-
E.
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.
- 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_69eff6ef211081909d31d9be5f5567e6 |
completed | April 27, 2026, 11:53 p.m. |
Created at: April 28, 2026, 1:10 a.m.