Triple
T22132901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maryland National Guard facilities |
E546949
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | National Guard infrastructure |
C1086
|
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 infrastructure Context triple: [Maryland National Guard facilities, instanceOf, National Guard infrastructure]
-
A.
National Defense Management Center
The National Defense Management Center is a centralized command and control facility responsible for coordinating, monitoring, and directing a nation's military and defense operations at the strategic level.
-
B.
military training infrastructure network
A military training infrastructure network is an integrated system of facilities, ranges, technologies, and support services designed to plan, deliver, and sustain training activities for armed forces across multiple locations.
-
C.
national security infrastructure
National security infrastructure is the integrated system of physical facilities, technologies, organizations, and legal frameworks designed to protect a nation’s sovereignty, critical assets, and population from internal and external threats.
-
D.
military installation
chosen
A military installation is a designated facility or area where armed forces are stationed, trained, equipped, and supported to conduct defense and security operations.
-
E.
United States Army installation
A United States Army installation is a designated military facility, base, or post that supports the housing, training, operations, logistics, and administration of Army personnel and equipment.
- 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_69e11e39bf348190b541bfa16a7b71e0 |
completed | April 16, 2026, 5:36 p.m. |
Created at: April 16, 2026, 8:32 p.m.