Triple

T15900001
Position Surface form Disambiguated ID Type / Status
Subject Cuyabeno Reserve buffer areas E385559 entity
Predicate instanceOf P0 FINISHED
Object protected area buffer 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: protected area buffer zone
Context triple: [Cuyabeno Reserve buffer areas, instanceOf, protected area buffer 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. 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.
  • C. Protected area designation
    A protected area designation is an official classification assigned to a geographic region to conserve its natural, cultural, or ecological values by regulating human activities and land use.
  • D. protected landscape area
    A protected landscape area is a designated region where the interaction of people and nature over time has produced a distinct character with significant ecological, cultural, and scenic value that is conserved and managed through legal or other effective means.
  • E. Protected natural area
    A protected natural area is a geographically defined space designated and managed to conserve biodiversity, natural resources, and ecosystem services while limiting or regulating human activities.
  • 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_69d86da5b800819083a31be937d738b0 completed April 10, 2026, 3:25 a.m.
Created at: April 10, 2026, 4:51 a.m.