Triple
T26754319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Irwell via Bridgewater Canal |
E674630
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic waterway link |
C38759
|
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: historic waterway link Context triple: [River Irwell via Bridgewater Canal, instanceOf, historic waterway link]
-
A.
historic water feature
chosen
A historic water feature is a man-made or modified natural water element, such as a fountain, canal, pond, or well, that holds cultural, architectural, or historical significance within a landscape or built environment.
-
B.
historic portage route
A historic portage route is a traditional overland path used to carry watercraft and goods between navigable waterways, often significant for its cultural, economic, and transportation history.
-
C.
historic stream
A historic stream is a watercourse whose past physical characteristics, flow patterns, and ecological conditions are documented or inferred from historical records, maps, or observations, often differing from its present-day state.
-
D.
historic irrigation canal
A historic irrigation canal is a man-made waterway constructed in the past to divert and distribute water for agricultural use, often reflecting the engineering practices and socio-economic conditions of its time.
-
E.
restored waterway
A restored waterway is a previously degraded or altered river, stream, or canal that has been rehabilitated to improve its ecological function, water quality, and surrounding habitat while often enhancing recreational and aesthetic values.
- 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_69eecda6e9dc81908452fab3ba17ed9b |
completed | April 27, 2026, 2:44 a.m. |
Created at: April 27, 2026, 3:55 a.m.