Triple
T24109682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kachess Lake |
E597330
|
entity |
| Predicate | stateHydrologicSystem |
P2432
|
FINISHED |
| Object | Yakima River basin |
—
|
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: Yakima River basin | Statement: [Kachess Lake, stateHydrologicSystem, Yakima River basin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stateHydrologicSystem Context triple: [Kachess Lake, stateHydrologicSystem, Yakima River basin]
-
A.
hydrologicCodeSystem
Indicates the classification or coding system used to identify and organize hydrologic or water-related features.
-
B.
hasHydrologicalRegime
Indicates that one entity (typically a water body or hydrological system) is characterized by, or associated with, a particular pattern or regime of water flow and levels over time.
-
C.
waterwaySystem
chosen
Indicates that one entity is part of, or belongs to, a connected network of waterways associated with another entity.
-
D.
hydrologicUnitCode
Indicates the standardized hydrologic unit identifier that specifies the drainage or watershed area associated with a given geographic feature or location.
-
E.
hydrologyFeature
Indicates a relationship where one entity is a hydrological feature (such as a body or flow of water) associated with or characterizing another entity.
- 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_69e288c60f9c8190af948d7354aedbeb |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1de19ce048190aaa3b7b73db50e2f |
completed | April 29, 2026, 10:31 a.m. |
| PD | Predicate disambiguation | batch_69f17651458c8190bbfd301883e46085 |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:02 p.m.