Triple
T17879810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Officer Personnel Management Directorate |
E447052
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | U.S. Army directorate |
C39999
|
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 directorate Context triple: [Officer Personnel Management Directorate, instanceOf, U.S. Army directorate]
-
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.
U.S. Army program executive office
A U.S. Army program executive office is an organizational entity responsible for managing the life cycle of specific categories of Army acquisition programs, from development and procurement through sustainment and modernization.
-
C.
United States Army directive
A United States Army directive is an official, authoritative order or instruction issued by Army leadership that establishes or changes policy, procedures, responsibilities, or standards for the organization.
-
D.
U.S. Army institution
The U.S. Army institution is the formal organizational structure, culture, and governing framework that defines, supports, and regulates the United States Army’s missions, personnel, doctrine, and operations.
-
E.
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.
- F. None of above. chosen
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_69d8b9f4c22c819093c2680434472894 |
completed | April 10, 2026, 8:51 a.m. |
Created at: April 10, 2026, 10:18 a.m.