Triple
T12469943
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ellesmere Canal (historic) |
E298026
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic waterway project |
C26460
|
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 project Context triple: [Ellesmere Canal (historic), instanceOf, historic waterway project]
-
A.
engineered waterway
chosen
An engineered waterway is a human-made or heavily modified channel or system designed to control, convey, or manage water for purposes such as navigation, irrigation, drainage, flood control, or power generation.
-
B.
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.
-
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.
navigable waterway
A navigable waterway is a natural or artificial body of water, such as a river, canal, or channel, that is deep and wide enough for vessels to travel safely for transportation or commerce.
-
E.
baroque waterway
A baroque waterway is an ornately designed canal or watercourse, often integrated into grand landscapes or urban plans, characterized by elaborate curves, decorative features, and dramatic visual perspectives typical of the Baroque style.
- 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_69d6ada270808190b1a2b2e7b02bb426 |
completed | April 8, 2026, 7:33 p.m. |
Created at: April 8, 2026, 9:56 p.m.