Triple
T31016446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fukushima exclusion zone |
E790337
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | exclusion zone |
C56179
|
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: exclusion zone Context triple: [Fukushima exclusion zone, instanceOf, exclusion zone]
-
A.
protective zone
A protective zone is a designated area or boundary established to shield people, assets, or environments from potential harm, hazards, or unauthorized influence.
-
B.
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.
-
C.
exclusive economic zone
An exclusive economic zone (EEZ) is a sea zone extending up to 200 nautical miles from a coastal state's baseline, within which that state has special rights to explore, exploit, conserve, and manage natural resources, while other states retain freedoms of navigation and overflight.
-
D.
radioactively contaminated area
chosen
A radioactively contaminated area is a geographic location where radioactive substances are present at levels above natural background, posing potential health and environmental hazards.
-
E.
collision zone
A collision zone is a region where two or more entities, forces, or objects meet and interact with sufficient proximity or energy to produce impacts, exchanges, or transformations.
- 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_69f224c811508190a7de096a5b1f5798 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:57 p.m.