Triple
T36007737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Melbourne green corridor network |
E1041317
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | urban green infrastructure network |
C10628
|
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 green infrastructure network Context triple: [Melbourne green corridor network, instanceOf, urban green infrastructure network]
-
A.
landscape infrastructure
Landscape infrastructure is the integrated system of natural and designed land-based elements—such as greenways, parks, water systems, and ecological corridors—that together provide environmental, social, and economic services for a region.
-
B.
habitat network
chosen
A habitat network is an interconnected system of natural areas and corridors that facilitates the movement, survival, and genetic exchange of species across a landscape.
-
C.
urban environmental complex
An urban environmental complex is an integrated system of natural and built elements within a city—such as green spaces, water bodies, infrastructure, and human activities—that interact to shape the urban ecosystem’s ecological, social, and climatic conditions.
-
D.
urban park system component
An urban park system component is an individual physical or programmatic element—such as a park, trail, plaza, facility, or natural feature—that collectively contributes to the recreational, ecological, and social functions of a city’s interconnected green space network.
-
E.
urban structure
An urban structure is the physical and spatial arrangement of buildings, infrastructure, and public spaces that together form the functional and organizational framework of a city.
- 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_69f76e2a02208190aedd1f9025a8b300 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:07 p.m.