Triple
T35672085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peel Channel |
E1030746
|
entity |
| Predicate | isMajorDistributary |
P25047
|
FINISHED |
| Object | Peel 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: Peel River | Statement: [Peel Channel, isMajorDistributary, Peel River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMajorDistributary Context triple: [Peel Channel, isMajorDistributary, Peel River]
-
A.
isMajorRiver
Indicates that a river is classified as a major or significant river, typically based on factors like length, discharge, or geographic importance.
-
B.
distributaryOf
chosen
Indicates that one watercourse branches off from a main river or stream and carries its water away, rather than feeding into it.
-
C.
isMajorWatercourseOf
Indicates that a watercourse is a primary or significant river or stream associated with, or flowing through, a particular geographic area or feature.
-
D.
isMajorSalmonRiver
Indicates that a river is classified as one of the principal or most significant salmon-bearing rivers in a given region or context.
-
E.
isMinorRiver
Indicates that a river is relatively small in size, length, or importance compared to major rivers.
- 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_69f76e0acfc0819082c8495c2210ce73 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fdee770af48190aca2670db50f8b49 |
completed | May 8, 2026, 2:08 p.m. |
| PD | Predicate disambiguation | batch_69fdecec98a08190a357d816dc2a6dbe |
completed | May 8, 2026, 2:02 p.m. |
Created at: May 3, 2026, 4:05 p.m.