Triple
T34257430
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort Custer Military Reservation |
E878930
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Michigan Army National Guard facility |
C828
|
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: Michigan Army National Guard facility Context triple: [Fort Custer Military Reservation, instanceOf, Michigan Army National Guard facility]
-
A.
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.
-
B.
U.S. Army helicopter facility
A U.S. Army helicopter facility is a specialized military installation that supports the operation, maintenance, training, and deployment of Army rotary-wing aircraft and their crews.
-
C.
United States Army installation
chosen
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.
-
D.
United States Army training range
A United States Army training range is a designated area equipped and managed for conducting military training exercises, weapons qualification, and tactical simulations under controlled and safe conditions.
-
E.
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.
- 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_69f349b421cc8190b4b4655e1d612548 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 1:56 a.m.