Triple
T21857032
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bute Inlet fjord system |
E539654
|
entity |
| Predicate | hasHeadwaterRiver |
P140514
|
FINISHED |
| Object | Homathko 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: Homathko River | Statement: [Bute Inlet fjord system, hasHeadwaterRiver, Homathko River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHeadwaterRiver Context triple: [Bute Inlet fjord system, hasHeadwaterRiver, Homathko River]
-
A.
hasHeadwaterStatus
Indicates that a water body holds the status of being a headwater or source segment within a hydrological system.
-
B.
hasHeadwatersOf
chosen
Indicates that a specified location or feature is the source or origin point of a particular river or watercourse.
-
C.
hasHeadwatersIn
Indicates that the source or origin of a river, stream, or similar watercourse is located within a specified geographic area or feature.
-
D.
hasRiver
Indicates that a location or area contains, is traversed by, or is directly associated with a river.
-
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_69e0c47829648190bbe2d1d7033768ec |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f0d636dc708190be34bb7ea526cfac |
completed | April 28, 2026, 3:45 p.m. |
| PD | Predicate disambiguation | batch_69e6be9394f88190945ddd1dc004d29d |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 6:56 p.m.