Triple
T21179175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Riverbank Army Ammunition Plant (former) |
E521898
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | former United States Army ammunition plant |
C29458
|
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: former United States Army ammunition plant Context triple: [Riverbank Army Ammunition Plant (former), instanceOf, former United States Army ammunition plant]
-
A.
munitions facility
A munitions facility is an industrial site where explosive weapons, ammunition, and related components are manufactured, assembled, stored, and sometimes tested under controlled conditions.
-
B.
ordnance facility
chosen
An ordnance facility is a specialized site where military weapons, ammunition, and related explosive materials are manufactured, stored, maintained, and sometimes tested under controlled conditions.
-
C.
former military complex
A former military complex is a decommissioned installation once used for defense or armed forces operations, now repurposed, abandoned, or awaiting redevelopment.
-
D.
former United States Mint facility
A former United States Mint facility is a decommissioned government building that once produced or processed U.S. coinage and related monetary materials but is no longer in active minting operation.
-
E.
former industrial plant
A former industrial plant is a decommissioned facility that once housed large-scale manufacturing or processing operations, often leaving behind substantial physical infrastructure and potential environmental impacts.
- 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_69e0b50ef1d48190b063aa342667df22 |
completed | April 16, 2026, 10:08 a.m. |
Created at: April 16, 2026, 3 p.m.