Triple

T22609696
Position Surface form Disambiguated ID Type / Status
Subject National Reserve of Peru E566665 entity
Predicate hasStricterProtectionThan P29844 FINISHED
Object communal reserve 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: communal reserve | Statement: [National Reserve of Peru, hasStricterProtectionThan, communal reserve]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasStricterProtectionThan
Context triple: [National Reserve of Peru, hasStricterProtectionThan, communal reserve]
  • A. isStrongerProtectionThan chosen
    Indicates that one form of protection provides a higher level of security, defense, or safeguarding compared to another.
  • B. hasStrictProtection
    Indicates that an entity is subject to strong, enforceable safeguards or restrictions that tightly limit how it can be accessed, used, or altered.
  • C. hasStricterStandardThan
    Indicates that one entity’s rules, criteria, or requirements are more demanding or rigorous than those of another entity.
  • D. isProtectedBy
    Indicates that one entity provides protection, defense, or safeguarding for another entity.
  • E. isProtectedFor
    Indicates that one entity is safeguarded or preserved specifically for the benefit, use, or rights of another entity.
  • F. None of above.

Provenance (3 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_69e245884860819081046ce07d5872c4 completed April 17, 2026, 2:36 p.m.
NER Named-entity recognition batch_69f167e9245c81908e36ffcd16737a9d completed April 29, 2026, 2:07 a.m.
PD Predicate disambiguation batch_69ee627be4248190889a88764624e174 completed April 26, 2026, 7:07 p.m.
Created at: April 17, 2026, 2:56 p.m.