Triple
T37271706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Camp Swift |
E924530
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Texas Army National Guard installation |
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: Texas Army National Guard installation Context triple: [Camp Swift, instanceOf, Texas Army National Guard installation]
-
A.
Texas Army National Guard unit
A Texas Army National Guard unit is a state-based military organization composed of part-time citizen-soldiers who train regularly and can be mobilized for both state emergencies and federal missions.
-
B.
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.
-
C.
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.
-
D.
Utah Army National Guard training facility
A Utah Army National Guard training facility is a designated military site in Utah that provides soldiers with the infrastructure, ranges, and resources needed for readiness, skill development, and mission-specific training.
-
E.
Oklahoma Army National Guard unit
An Oklahoma Army National Guard unit is a state-based military organization composed of citizen-soldiers who train part-time to provide combat, support, and emergency response capabilities for both state and federal 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_69f76eacdd8c819094080d3991e6d37c |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:15 p.m.