Triple
T19369894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Coast–Hunter corridor |
E484504
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional growth corridor |
C2218
|
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: regional growth corridor Context triple: [Central Coast–Hunter corridor, instanceOf, regional growth corridor]
-
A.
development corridor
chosen
A development corridor is a strategically planned geographic area, often aligned along major transportation routes, where concentrated investment in infrastructure, industry, and services is used to stimulate economic growth and regional integration.
-
B.
population corridor
A population corridor is a geographic or infrastructural pathway that facilitates the movement, interaction, and distribution of people between distinct population centers.
-
C.
suburban railway corridor
A suburban railway corridor is a dedicated rail route connecting city centers with surrounding residential suburbs, designed to support frequent, high-capacity commuter train services.
-
D.
regional axis
A regional axis is a conceptual line or direction that organizes, connects, or structures spatial relationships and activities across a defined geographic region.
-
E.
regional economic zone
A regional economic zone is a geographically defined area within or across countries where economic policies, regulations, and incentives are coordinated to promote trade, investment, and 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_69d8e8d305088190ad13571532aa454c |
completed | April 10, 2026, 12:10 p.m. |
Created at: April 10, 2026, 1:35 p.m.