Triple
T1951105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Army service component command |
E42158
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | type of military command |
C1992
|
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: type of military command Context triple: [Army service component command, instanceOf, type of military command]
-
A.
major command of the United States Army
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.
-
B.
military office
A military office is an administrative workspace within an armed forces organization where personnel manage planning, logistics, communication, and documentation to support military operations.
-
C.
United States Army command
chosen
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.
-
D.
military officer
A military officer is a formally commissioned leader in the armed forces responsible for planning, directing, and managing operations, personnel, and resources to achieve strategic and tactical objectives.
-
E.
military organization
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.
- 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_69a8870e08fc8190a319cbf2600db15f |
completed | March 4, 2026, 7:25 p.m. |
Created at: March 4, 2026, 7:36 p.m.