Triple

T24148422
Position Surface form Disambiguated ID Type / Status
Subject McLeod Lake E598455 entity
Predicate isInDrainageRegion P113991 FINISHED
Object interior British Columbia watershed 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: interior British Columbia watershed | Statement: [McLeod Lake, isInDrainageRegion, interior British Columbia watershed]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isInDrainageRegion
Context triple: [McLeod Lake, isInDrainageRegion, interior British Columbia watershed]
  • A. isInCatchment chosen
    Indicates that one entity lies within the geographic or service area covered or served by another entity.
  • B. hasDrainage
    Indicates that one entity serves as the drainage system or outlet through which another entity’s liquid or runoff is removed or discharged.
  • C. drainageInfluencedBy
    Indicates that the pattern, direction, or effectiveness of drainage is affected or controlled by another factor or entity.
  • D. hasPositionInWatercourse
    Indicates that one entity occupies a specific location or position within the course of a body of water.
  • E. isOnWatercourse
    Indicates that one entity is situated directly on, above, or along the path of a watercourse such as a river, stream, or canal.
  • 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_69e288c9e488819093dd1acd91b08b8a completed April 17, 2026, 7:23 p.m.
NER Named-entity recognition batch_69f1e00d252c8190a02bec29189baad0 completed April 29, 2026, 10:40 a.m.
PD Predicate disambiguation batch_69f1765650fc8190a6bc1eb512b240bf completed April 29, 2026, 3:09 a.m.
Created at: April 17, 2026, 11:30 p.m.