Triple
T8921086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chernobyl Exclusion Zone |
E212416
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | radioactive 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 exclusion zone Context triple: [Chernobyl Exclusion Zone, instanceOf, radioactive 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.
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.
-
C.
nuclear attack
A nuclear attack is a deliberate military or terrorist action involving the detonation or threatened use of nuclear weapons to cause massive destruction, casualties, and strategic disruption.
-
D.
health zone
A health zone is a designated area or region where healthcare services, resources, and policies are organized and managed to support and improve the health of the population within its boundaries.
-
E.
no-take zone
A no-take zone is a designated area, typically in a marine or freshwater environment, where all forms of extractive activities such as fishing, mining, and harvesting are strictly prohibited to protect ecosystems and biodiversity.
- 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_69ca839481d48190b42b037e0d0f636c |
completed | March 30, 2026, 2:07 p.m. |
Created at: March 30, 2026, 6:56 p.m.