Triple
T30131595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belarusian Exclusion Zone |
E765859
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | radioactive contamination exclusion zone |
C22870
|
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: radioactive contamination exclusion zone Context triple: [Belarusian Exclusion Zone, instanceOf, radioactive contamination exclusion zone]
-
A.
protective zone
chosen
A protective zone is a designated area or boundary established to shield people, assets, or environments from potential harm, hazards, or unauthorized influence.
-
B.
radiation containment structure
A radiation containment structure is a protective enclosure designed to prevent the escape of harmful ionizing radiation from sources such as nuclear reactors, medical equipment, or radioactive materials into the surrounding environment.
-
C.
radioactive material
Radioactive material is any substance that contains unstable atomic nuclei which spontaneously emit ionizing radiation as they decay into more stable forms.
-
D.
radioactive substances regulation
Radioactive substances regulation encompasses the laws, standards, and oversight mechanisms that control the production, use, transport, and disposal of radioactive materials to protect human health and the environment.
-
E.
military-controlled zone
A military-controlled zone is a designated geographic area where military authorities exercise primary control over security, movement, and activities, often restricting civilian access and enforcing special regulations.
- 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_69f22477d1a081908df2b7e6ed16859d |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:15 p.m.