Triple

T9222014
Position Surface form Disambiguated ID Type / Status
Subject Parinacota Province E221582 entity
Predicate hasProtectedAreaCoverage P87662 FINISHED
Object high 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: high | Statement: [Parinacota Province, hasProtectedAreaCoverage, high]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasProtectedAreaCoverage
Context triple: [Parinacota Province, hasProtectedAreaCoverage, high]
  • A. hasProtectedArea
    Indicates that an entity possesses, includes, or is associated with a designated protected area for conservation or restricted use.
  • B. hasProtectedAreaStatus
    Indicates that an area is officially designated and managed as a protected area under relevant conservation or legal frameworks.
  • C. hasProtectedAreaAccess
    Indicates that an entity is permitted to enter, use, or otherwise access a designated protected area under defined conditions.
  • D. hasProtectedAreaCategory
    Indicates that an area is assigned a specific protection or conservation category under a recognized protected area classification system.
  • E. hasProtectedAreaAuthority
    Indicates that an entity holds official authority or responsibility for managing or overseeing a protected area.
  • 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_69ca83ec8db08190a9110df8232885d2 completed March 30, 2026, 2:08 p.m.
NER Named-entity recognition batch_69ccda76e3648190af9e24381db7679a completed April 1, 2026, 8:42 a.m.
PD Predicate disambiguation batch_69cc7a3daeb481908b0abde3fbc1f1f0 completed April 1, 2026, 1:51 a.m.
PDg Predicate description generation batch_69cc95597be081908ece2491dd2f0f74 completed April 1, 2026, 3:47 a.m.
Created at: March 30, 2026, 7:28 p.m.