Triple

T20726219
Position Surface form Disambiguated ID Type / Status
Subject Nass Ranges E509441 entity
Predicate encompassesHeadwatersOf P140514 FINISHED
Object Nass River 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: Nass River | Statement: [Nass Ranges, encompassesHeadwatersOf, Nass River]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: encompassesHeadwatersOf
Context triple: [Nass Ranges, encompassesHeadwatersOf, Nass River]
  • A. hasHeadwatersOf chosen
    Indicates that a specified location or feature is the source or origin point of a particular river or watercourse.
  • B. hasHeadwatersIn
    Indicates that the source or origin of a river, stream, or similar watercourse is located within a specified geographic area or feature.
  • C. oneOfTwoHeadwatersOf
    Indicates that an entity is one of the two primary sources or starting points (headwaters) of another entity, typically a river or stream.
  • D. isMajorWatercourseOf
    Indicates that a watercourse is a primary or significant river or stream associated with, or flowing through, a particular geographic area or feature.
  • E. formsHeadwatersWith
    Indicates that two or more watercourses join or originate together to create the initial source or headwaters of a larger river or stream.
  • 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_69e0b4c4cc648190b45fda6e2b20af56 completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6c1e8b020819091d5788b90215ead completed April 21, 2026, 12:16 a.m.
PD Predicate disambiguation batch_69e5c04b31248190b9b9d91b5cb854e3 completed April 20, 2026, 5:57 a.m.
Created at: April 16, 2026, 12:29 p.m.