Triple
T22070798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Army Department of Arizona |
E545399
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | U.S. Army military department |
C45756
|
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 military department Context triple: [U.S. Army Department of Arizona, instanceOf, U.S. Army military department]
-
A.
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.
-
B.
branch of the United States Army
A branch of the United States Army is a specialized functional category, such as Infantry or Signal Corps, that organizes soldiers, training, and equipment around a distinct mission set and expertise area within the Army.
-
C.
U.S. Army directorate
A U.S. Army directorate is a high-level organizational unit within the Army responsible for overseeing and coordinating specific functional areas, policies, and programs to support the service’s overall mission.
-
D.
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.
-
E.
component of the United States Army
A component of the United States Army is a major organizational subdivision, such as the Active Army, Army National Guard, or Army Reserve, that collectively contributes to the Army’s overall mission and capabilities.
- 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_69e11e344dfc81909b1d88a7221329c7 |
completed | April 16, 2026, 5:36 p.m. |
Created at: April 16, 2026, 8:28 p.m.