Triple
T34575351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rochor River (historical alignment context) |
E887737
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | former river course |
C45054
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: former river course Context triple: [Rochor River (historical alignment context), instanceOf, former river course]
-
A.
former riverbed
chosen
A former riverbed is the abandoned channel or course where a river once flowed, now typically filled with sediments, vegetation, or repurposed landforms.
-
B.
former surface river
A former surface river is a once-active, above-ground watercourse that has ceased to flow or has been diverted, leaving behind geomorphic or ecological evidence of its past presence.
-
C.
former name of a river
A former name of a river is a historical or obsolete designation once used to identify a specific river, typically replaced due to cultural, political, or linguistic changes.
-
D.
former canal
A former canal is a disused or decommissioned artificial waterway that once facilitated transportation, irrigation, or drainage but no longer serves its original function.
-
E.
former waterfall
A former waterfall is a geological feature where a waterfall once existed but has since disappeared due to processes like erosion, river course changes, or human intervention, leaving behind characteristic landforms such as dry falls, plunge pools, or abandoned channels.
- F. None of above.
Provenance (1 batch)
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_69f349d1a5fc81908557a46875b2f157 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 2:03 a.m.