Triple

T23343108
Position Surface form Disambiguated ID Type / Status
Subject Everest region E591784 entity
Predicate protectedAreaFramework P67265 FINISHED
Object Sagarmatha National Park regulations 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: Sagarmatha National Park regulations | Statement: [Everest region, protectedAreaFramework, Sagarmatha National Park regulations]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: protectedAreaFramework
Context triple: [Everest region, protectedAreaFramework, Sagarmatha National Park regulations]
  • A. protectedAreaAssociation
    Indicates an association where one entity is designated as, or linked to, a protected area in relation to another entity.
  • B. protectedAreaCore
    Indicates that an entity lies within the core, most strictly protected zone of a designated protected area.
  • C. protectedAreaCountry
    Indicates that a protected area is located within and legally falls under the jurisdiction of a specific country.
  • D. governingProtectedArea chosen
    Indicates that one entity has official authority to manage, regulate, or oversee the protection and administration of a designated protected area.
  • E. protectedAreaEstablished
    Indicates that a designated protected area has been formally created or brought into legal existence.
  • 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_69e25d20e3d08190bcede87673cafb25 completed April 17, 2026, 4:17 p.m.
NER Named-entity recognition batch_69f1983431f08190b0078728d44872a8 completed April 29, 2026, 5:33 a.m.
PD Predicate disambiguation batch_69effcfd8d288190937a887fe6023c11 completed April 28, 2026, 12:19 a.m.
Created at: April 17, 2026, 5:18 p.m.