Triple
T11350425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I Corps military community |
E268825
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | U.S. Army installation community |
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: U.S. Army installation community Context triple: [I Corps military community, instanceOf, U.S. Army installation community]
-
A.
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.
-
B.
U.S. Army center of excellence
A U.S. Army center of excellence is an institutional organization that develops, integrates, and advances specialized doctrine, training, capabilities, and expertise for a specific warfighting or functional area across the Army.
-
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.
military community
A military community is a social group composed of service members, their families, veterans, and supporting personnel who share common experiences, resources, and culture related to military life.
-
E.
U.S. Army sustainment command
The U.S. Army Sustainment Command is the organization responsible for providing logistics, supply, maintenance, and distribution support to ensure Army forces are equipped and sustained during training, deployment, and combat operations worldwide.
- 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_69d6aacbe18081909e5fadb50082dd96 |
completed | April 8, 2026, 7:21 p.m. |
Created at: April 8, 2026, 9:33 p.m.