Triple

T28737347
Position Surface form Disambiguated ID Type / Status
Subject Coquitlam Lake reservoir E730835 entity
Predicate waterQualityProtected P26290 FINISHED
Object true 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: true | Statement: [Coquitlam Lake reservoir, waterQualityProtected, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: waterQualityProtected
Context triple: [Coquitlam Lake reservoir, waterQualityProtected, true]
  • A. waterQualityProtection chosen
    Indicates efforts, measures, or responsibilities aimed at preserving or improving the cleanliness, safety, and ecological integrity of water resources.
  • B. hasWaterQualityDesignation
    Indicates that an entity has been assigned a specific official classification or status regarding its water quality.
  • C. waterQualityUse
    Indicates the way in which water quality is evaluated, classified, or applied for specific purposes or uses.
  • D. hasProtectedWatershed
    Indicates that an entity possesses or is associated with a watershed area that is legally or formally protected for conservation or resource management purposes.
  • E. hasWaterQualityImportance
    Indicates that something plays a significant role in determining, influencing, or assessing the quality of water.
  • 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_69f043eae0908190b28ce314686247d7 completed April 28, 2026, 5:21 a.m.
NER Named-entity recognition batch_69f73ae120bc8190bff94d38d7a7a00d completed May 3, 2026, 12:09 p.m.
PD Predicate disambiguation batch_69f73a38d0848190aa5139144b8561c6 completed May 3, 2026, 12:06 p.m.
Created at: April 28, 2026, 6:01 a.m.