Triple
T21667519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Las Terrazas community |
E534759
|
entity |
| Predicate | biosphereReserveZone |
P145375
|
FINISHED |
| Object | buffer zone |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: buffer zone | Statement: [Las Terrazas community, biosphereReserveZone, buffer zone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: biosphereReserveZone Context triple: [Las Terrazas community, biosphereReserveZone, buffer zone]
-
A.
biosphereReserveDesignationBy
Indicates that a biosphere reserve receives its official designation or status from a particular authority or organization.
-
B.
biosphereReserveType
Indicates the specific classification or category of a biosphere reserve within a defined typology or management framework.
-
C.
hasUNESCOBiosphereReserve
Indicates that an entity includes, contains, or is associated with a designated UNESCO Biosphere Reserve.
-
D.
UNESCOBiosphereReserveName
Indicates that an entity has the specified name as its UNESCO Biosphere Reserve designation.
-
E.
countryProtectedAreaSystem
Indicates that a country has an established system or network of designated protected areas under its jurisdiction.
- F. None of above. chosen
Provenance (4 batches)
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_69e0c46898008190aa618a4af55bd1ee |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef6c0cf6208190a8bd9fa423c65a40 |
completed | April 27, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69e6968abfdc81909cf9e0bd72db9eca |
completed | April 20, 2026, 9:11 p.m. |
| PDg | Predicate description generation | batch_69e69cb4bcbc8190a4fc2d508df107be |
completed | April 20, 2026, 9:37 p.m. |
Created at: April 16, 2026, 6:37 p.m.