Triple
T5756484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Gunpowder Mills |
E126980
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | former explosives factory |
C5370
|
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 explosives factory Context triple: [Royal Gunpowder Mills, instanceOf, former explosives factory]
-
A.
former industrial plant
chosen
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.
-
B.
nuclear weapons assembly plant
A nuclear weapons assembly plant is a highly secure industrial facility where nuclear and non-nuclear components are manufactured, integrated, and tested to produce complete nuclear weapons in compliance with strict safety, security, and regulatory standards.
-
C.
former nuclear test site
A former nuclear test site is a geographically defined area where nuclear weapons or devices were previously detonated for testing purposes and which may still be subject to environmental monitoring, contamination concerns, and restricted use.
-
D.
former armory
A former armory is a building originally constructed or used for storing and maintaining weapons and military equipment that has since been decommissioned or repurposed for other functions.
-
E.
weapons-grade plutonium production facility
A weapons-grade plutonium production facility is an industrial complex designed to produce, extract, and process plutonium with isotopic compositions suitable for use in nuclear weapons.
- 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_69c00833a3fc81908f4bc29ed011b7a6 |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 3:49 p.m.