Triple
T17527018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Calabazas Creek (via connected flood-control system) |
E426823
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | engineered urban waterway |
C17618
|
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: engineered urban waterway Context triple: [Calabazas Creek (via connected flood-control system), instanceOf, engineered urban waterway]
-
A.
engineered waterway
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.
urban watercourse
chosen
An urban watercourse is a natural or engineered channel of flowing water that runs through a city or town, shaped and managed by surrounding urban infrastructure and land use.
-
C.
waterfront greenway
A waterfront greenway is a linear, publicly accessible open space along a body of water that combines pedestrian and bicycle paths with landscaping, recreation areas, and ecological features to connect communities and enhance shoreline environments.
-
D.
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.
-
E.
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.
- 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_69d889de677081909b22d2657b1f0292 |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:49 a.m.