Triple
T14161118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USARAF |
E350946
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | United States Army service component command |
C33526
|
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: United States Army service component command Context triple: [USARAF, instanceOf, United States Army service component 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.
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.
-
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.
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.
- 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_69d8278775fc8190b0802d22ca2f495d |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 12:59 a.m.