Triple
T21984018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | readiness command |
E542911
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | U.S. Army organizational role |
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: U.S. Army organizational role Context triple: [readiness command, instanceOf, U.S. Army organizational role]
-
A.
U.S. Army organizational element
A U.S. Army organizational element is a structured unit of soldiers, equipment, and command relationships designed to perform specific missions within the Army’s overall force hierarchy.
-
B.
United States Army position
A United States Army position is a specific role or job within the Army’s organizational structure, defined by rank, responsibilities, and duties in support of military operations and administration.
-
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.
United States military staff organization
A United States military staff organization is a structured group of officers and enlisted personnel organized into functional sections (e.g., personnel, intelligence, operations, logistics) that support a commander in planning, coordinating, and executing missions.
-
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.
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_69e0c48136b081908831fa907cc02e18 |
completed | April 16, 2026, 11:14 a.m. |
Created at: April 16, 2026, 8:04 p.m.