Triple
T8261104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adriaen’s Landing development |
E193195
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | riverfront revitalization project |
C10710
|
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: riverfront revitalization project Context triple: [Adriaen’s Landing development, instanceOf, riverfront revitalization project]
-
A.
waterfront revitalization plan
chosen
A waterfront revitalization plan is a comprehensive strategy to transform underused or deteriorated shoreline areas into vibrant, accessible, and sustainable public and economic spaces.
-
B.
waterfront district
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.
waterfront development site
A waterfront development site is a designated parcel of land adjacent to a body of water that is planned or suitable for construction and mixed-use projects leveraging water access and views.
-
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.
waterfront street
A waterfront street is a public roadway or pedestrian thoroughfare that runs directly alongside a body of water, often featuring views, access points, and amenities oriented toward the shoreline.
- 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_69ca82e081d48190986beaa51f498ab9 |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 5:49 p.m.