Triple
T12919976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maryland National Guard |
E309090
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | National Guard component |
C14680
|
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: National Guard component Context triple: [Maryland National Guard, instanceOf, National Guard component]
-
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.
component of the United States Armed Forces
chosen
A component of the United States Armed Forces is an organizational subdivision, such as a service branch, reserve, or specialized command, that contributes distinct capabilities and personnel to the nation’s overall military structure and missions.
-
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.
military unit component
A military unit component is an individual sub-unit or element, such as a squad, platoon, or company, that combines with others to form a larger organized military force.
-
E.
auxiliary military force
An auxiliary military force is a supplementary, often non-regular or part-time armed organization that supports a nation’s primary military through additional manpower, specialized skills, or local defense roles.
- 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_69d7bdf92b588190acdf2a2291ac4590 |
completed | April 9, 2026, 2:55 p.m. |
Created at: April 9, 2026, 5:41 p.m.