Triple
T27091167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Military Division of the Missouri |
E686171
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | U.S. Army administrative command |
C2646
|
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: U.S. Army administrative command Context triple: [Military Division of the Missouri, instanceOf, U.S. Army administrative command]
-
A.
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.
-
B.
United States Army service component command
A United States Army service component command is the Army organization assigned to support, integrate, and provide Army forces to a specific unified combatant command, serving as its primary Army headquarters for planning and operations.
-
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.
United States Army major command
A United States Army major command is a high-level organizational entity responsible for overseeing and directing large-scale Army operations, resources, and support functions within a specific mission area or geographic region.
-
E.
major command of the United States Army
chosen
A major command of the United States Army is a high-level organizational entity responsible for overseeing, directing, and supporting large-scale operational, administrative, or functional missions across multiple subordinate units and installations.
- 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_69ef148940ec819097b5c20fbfbf7c81 |
completed | April 27, 2026, 7:47 a.m. |
Created at: April 27, 2026, 8:40 a.m.