Triple
T38525808
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Standby Reserve |
E923224
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | U.S. military personnel reserve status |
C30929
|
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. military personnel reserve status Context triple: [Standby Reserve, instanceOf, U.S. military personnel reserve status]
-
A.
armed forces reserve
An armed forces reserve is a military component composed of trained personnel who are not in full-time active service but can be mobilized to support or augment regular forces during emergencies, conflicts, or special operations.
-
B.
United States military reserve component category
chosen
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.
-
C.
United States military position
A United States military position is a formally defined role within the U.S. Armed Forces that carries specific duties, authority, rank, and responsibilities in support of national defense and military operations.
-
D.
American military personnel
American military personnel are individuals who serve in the United States Armed Forces, including the Army, Navy, Air Force, Marine Corps, Space Force, and Coast Guard, in roles ranging from combat and support to technical and administrative duties.
-
E.
Army Reserve formation
An Army Reserve formation is an organized military unit composed of part-time soldiers who train regularly and can be mobilized to support active-duty forces during operations, emergencies, or wartime.
- 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_69f76ea8f6348190a5c03fb6292bbee3 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:32 p.m.