Triple
T31662515
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lower Yukon region |
E808038
|
entity |
| Predicate | hasPrimaryRiverSection |
P116240
|
FINISHED |
| Object | lower Yukon 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: lower Yukon River | Statement: [Lower Yukon region, hasPrimaryRiverSection, lower Yukon River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryRiverSection Context triple: [Lower Yukon region, hasPrimaryRiverSection, lower Yukon River]
-
A.
hasSectionDefinedByRiver
Indicates that a spatial entity has a portion or segment whose boundary or extent is determined by a river.
-
B.
watercourseSectionOf
Indicates that a watercourse segment forms a constituent part of a larger watercourse.
-
C.
downstreamRiverSection
Indicates that one river section is located downstream from, and receives flow from, another river section.
-
D.
isMajorRiver
Indicates that a river is classified as a major or significant river, typically based on factors like length, discharge, or geographic importance.
-
E.
includesHydrologicalSection
chosen
Indicates that one entity contains or encompasses a specific hydrological section as part of its spatial or structural extent.
- 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_69f348dbeef4819080b446a7feb6340b |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a0079e152648190a9da2add94fc1831 |
completed | May 10, 2026, 12:28 p.m. |
| PD | Predicate disambiguation | batch_6a0078f77f9c8190af357a6016a2bd53 |
completed | May 10, 2026, 12:24 p.m. |
Created at: April 30, 2026, 10:57 p.m.