Triple

T31350521
Position Surface form Disambiguated ID Type / Status
Subject Cobbinshaw Reservoir E799575 entity
Predicate isInProtectedAreaNetwork P58142 FINISHED
Object Scottish SSSI network NE NERFINISHED

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: Scottish SSSI network | Statement: [Cobbinshaw Reservoir, isInProtectedAreaNetwork, Scottish SSSI network]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isInProtectedAreaNetwork
Context triple: [Cobbinshaw Reservoir, isInProtectedAreaNetwork, Scottish SSSI network]
  • A. isInProtectedArea
    Indicates that an entity is located within a designated protected or conservation area.
  • B. isInProtectedAreaVicinity
    Indicates that an entity is located close to, but not necessarily within, a designated protected area.
  • C. partOfProtectedAreaNetwork chosen
    Indicates that an area is included within and contributes to a designated network of protected areas.
  • D. isProtectedAreaOf
    Indicates that a designated protected area (such as a park or reserve) is established to conserve and manage a specific geographic region or natural feature.
  • E. hasProtectedAreaStatus
    Indicates that an area is officially designated and managed as a protected area under relevant conservation or legal frameworks.
  • 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_69f224e51614819083141459a080e97c completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69f69f40ae2481909321485a3f63a3e4 completed May 3, 2026, 1:05 a.m.
PD Predicate disambiguation batch_69f69d1d25e88190a7f57d323574da90 completed May 3, 2026, 12:55 a.m.
Created at: April 29, 2026, 9:17 p.m.