Triple
T19345952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baltimore Wharf development |
E483877
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | waterfront regeneration 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: waterfront regeneration project Context triple: [Baltimore Wharf development, instanceOf, waterfront regeneration 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 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.
-
C.
waterfront site
A waterfront site is a parcel of land directly adjacent to a body of water, whose location, access, and environmental conditions are fundamentally shaped by its shoreline interface.
-
D.
waterfront hub
A waterfront hub is a central, mixed-use area located along a body of water that concentrates transportation, commerce, recreation, and social activities to connect people with the waterfront.
-
E.
waterfront public space
A waterfront public space is a shared, accessible area along a body of water designed for recreation, social interaction, and enjoyment of the natural and urban waterfront environment.
- 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_69d8e8d244f8819080eb1f3491300db2 |
completed | April 10, 2026, 12:10 p.m. |
Created at: April 10, 2026, 1:34 p.m.