Triple
T28357989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grave Creek to Foster Bar run |
E718286
|
entity |
| Predicate | riverSectionOf |
P120790
|
FINISHED |
| Object | Rogue 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: Rogue River | Statement: [Grave Creek to Foster Bar run, riverSectionOf, Rogue River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riverSectionOf Context triple: [Grave Creek to Foster Bar run, riverSectionOf, Rogue River]
-
A.
watercourseSectionOf
chosen
Indicates that a watercourse segment forms a constituent part of a larger watercourse.
-
B.
downstreamRiverSection
Indicates that one river section is located downstream from, and receives flow from, another river section.
-
C.
isWatercourseOf
Indicates that a watercourse (such as a river or stream) flows through, belongs to, or is geographically associated with a particular area or feature.
-
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.
raceRiver
Indicates that an entity participates in a race that takes place on or along a river.
- 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_69eff6ec27b481908c8d7b86c47893d9 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f68805b4848190b75da14996d52a38 |
completed | May 2, 2026, 11:25 p.m. |
| PD | Predicate disambiguation | batch_69f68609c0b08190a8e1238a4d97c270 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 28, 2026, 12:50 a.m.