Triple
T34080926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lancaster riverside regeneration |
E874038
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | riverside regeneration scheme |
C5822
|
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: riverside regeneration scheme Context triple: [Lancaster riverside regeneration, instanceOf, riverside regeneration scheme]
-
A.
riverside complex
A riverside complex is a multi-use development situated along a riverbank that typically integrates residential, commercial, recreational, and public spaces designed to engage with the waterfront environment.
-
B.
redeveloped docklands site
A redeveloped docklands site is a former industrial waterfront area transformed into a mixed-use urban district featuring modern housing, offices, leisure facilities, and improved public spaces while retaining elements of its maritime heritage.
-
C.
riverside location
A riverside location is a place situated directly along the banks of a river, characterized by its proximity to flowing water and the environmental, recreational, or economic activities it supports.
-
D.
riverside parklands
Riverside parklands are public green spaces located along riverbanks that provide recreational areas, natural habitat, and scenic corridors integrating water, vegetation, and human use.
-
E.
urban regeneration area
chosen
An urban regeneration area is a designated part of a city targeted for coordinated physical, economic, social, and environmental improvements to reverse decline and promote sustainable development.
- 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_69f349a61d448190b74642f325d3eb7a |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 1:52 a.m.