Triple
T22989211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kangson enrichment site (alleged) |
E572000
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | suspected uranium enrichment facility |
C6992
|
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: suspected uranium enrichment facility Context triple: [Kangson enrichment site (alleged), instanceOf, suspected uranium enrichment facility]
-
A.
uranium enrichment facility
chosen
A uranium enrichment facility is an industrial complex that increases the concentration of the fissile isotope U-235 in uranium to produce fuel for nuclear reactors or material for nuclear weapons.
-
B.
uranium processing facility
A uranium processing facility is an industrial plant where uranium ore is refined, converted, and prepared into nuclear-grade materials for use in fuel production or other nuclear applications.
-
C.
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.
-
D.
nuclear weapons production facility
A nuclear weapons production facility is a highly secured industrial complex where fissile materials are processed and assembled into components and complete systems for nuclear armaments.
-
E.
nuclear weapons component plant
A nuclear weapons component plant is an industrial facility dedicated to designing, manufacturing, and assembling specialized parts and subsystems used in the construction and maintenance of 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_69e245b535808190adef8a9df3c584db |
completed | April 17, 2026, 2:37 p.m. |
Created at: April 17, 2026, 3:49 p.m.