Triple
T16255318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ohio River waterfront in Louisville |
E394612
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | urban riverfront area |
C1079
|
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: urban riverfront area Context triple: [Ohio River waterfront in Louisville, instanceOf, urban riverfront area]
-
A.
urban watercourse
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.
-
B.
waterfront district
chosen
A waterfront district is an urban or suburban area located along a body of water, characterized by mixed-use development, public access to the shoreline, and activities centered around recreation, commerce, and scenic views.
-
C.
urban park
An urban park is a publicly accessible green space within a city that provides recreational areas, natural scenery, and social gathering places for residents and visitors.
-
D.
urban plaza
An urban plaza is a publicly accessible open space within a city, typically surrounded by buildings and streets, designed to support social interaction, circulation, and civic activities.
-
E.
urban regeneration area
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_69d87f2171208190951025e526947816 |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 10, 2026, 5:04 a.m.