Triple
T14913562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Troop Program Units |
E371325
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | U.S. Army Reserve unit type |
C26652
|
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 Reserve unit type Context triple: [Troop Program Units, instanceOf, U.S. Army Reserve unit type]
-
A.
United States military reserve component category
A United States military reserve component category is a classification that defines the status, service obligations, and readiness level of personnel serving in the Reserve or National Guard forces.
-
B.
Primary Reserve infantry regiment
A Primary Reserve infantry regiment is a part-time, volunteer military unit that provides trained infantry soldiers to support and augment a nation's regular army during operations, emergencies, and domestic tasks.
-
C.
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.
-
D.
U.S. Army organizational element
chosen
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.
-
E.
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.
- 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_69d85cc7ea3481908228b5acb7d06f12 |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 2:27 a.m.