Triple
T12754109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Konak coastal corridor |
E304812
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | waterfront transit corridor |
C21436
|
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 transit corridor Context triple: [Konak coastal corridor, instanceOf, waterfront transit corridor]
-
A.
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.
-
B.
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.
-
C.
planned transit corridor
chosen
A planned transit corridor is a designated route or area reserved for future development of public transportation infrastructure, such as bus rapid transit or rail lines, to guide growth and improve regional mobility.
-
D.
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.
-
E.
public transit system
A public transit system is an organized network of shared transportation services—such as buses, trains, subways, and trams—designed to move large numbers of people efficiently within and between urban and regional areas.
- 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_69d7bdf1fcd081909ffb0e0d6fa3a07d |
completed | April 9, 2026, 2:55 p.m. |
Created at: April 9, 2026, 5:27 p.m.