Triple
T32185726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Space National Guard (planned) |
E822103
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | proposed reserve component |
C5397
|
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: proposed reserve component Context triple: [Space National Guard (planned), instanceOf, proposed reserve component]
-
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.
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.
-
C.
reserve component
chosen
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.
-
D.
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.
-
E.
naval reserve force
A naval reserve force is a component of a nation's navy composed of trained personnel who serve part-time and can be mobilized to support or augment regular naval operations during emergencies, conflicts, or special missions.
- 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_69f3490755288190aee11740a34862f9 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:35 a.m.