Triple
T2667081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Individual Ready Reserve |
E55661
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | reserve component personnel category |
C9589
|
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: reserve component personnel category Context triple: [Individual Ready Reserve, instanceOf, reserve component personnel category]
-
A.
reserve component
A reserve component is a supplementary part of a system or organization that remains available for use when primary resources are insufficient, unavailable, or require reinforcement.
-
B.
military personnel category
chosen
A military personnel category is a classification that groups service members based on roles, ranks, duties, or service status within the armed forces.
-
C.
reserve component of the United States Air Force
The reserve component of the United States Air Force is the part-time military force composed of Air Force Reserve and Air National Guard units that support and augment the active-duty Air Force during peacetime and wartime operations.
-
D.
reserve team
A reserve team is a secondary squad of players within a sports club, primarily used for developing talent, providing match practice, and offering backup to the main (first) team.
-
E.
occupation authority component
An occupation authority component is a system element responsible for defining, managing, and enforcing rules, permissions, and responsibilities associated with specific roles or professions within an organizational or regulatory context.
- 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_69ab49e54de48190be708cd1cf8be073 |
completed | March 6, 2026, 9:40 p.m. |
Created at: March 6, 2026, 9:54 p.m.