Triple

T7551067
Position Surface form Disambiguated ID Type / Status
Subject UNESCO World Heritage buffer boundary E178534 entity
Predicate instanceOf P0 FINISHED
Object protective 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: protective zone
Context triple: [UNESCO World Heritage buffer boundary, instanceOf, protective zone]
  • A. protected area portion
    A protected area portion is a spatially defined subset of a larger protected area that is managed or designated for specific conservation, regulatory, or land-use purposes.
  • 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. type of protected area
    A type of protected area is a designated geographic space, recognized and managed through legal or other effective means, to achieve long-term conservation of nature and associated ecosystem services and cultural values.
  • D. 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.
  • E. Special Area of Conservation
    A Special Area of Conservation is a protected site designated under the EU Habitats Directive to safeguard rare, endangered, or vulnerable natural habitats and species of European importance.
  • F. None of above. chosen

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_69c69f2cbe08819088f9eb0c03ef529b completed March 27, 2026, 3:15 p.m.
Created at: March 27, 2026, 3:49 p.m.