Triple
T4191163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Birmingham metropolitan area green space network |
E89039
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | green space 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: green space network Context triple: [Birmingham metropolitan area green space network, instanceOf, green space network]
-
A.
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.
-
B.
greenway
A greenway is a linear, often vegetated corridor of land or water designed primarily for recreation, conservation, and non-motorized transportation.
-
C.
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.
-
D.
urban park
An urban park is a publicly accessible green space within a city that provides recreational areas, natural scenery, and social gathering places for residents and visitors.
-
E.
pedestrian network
A pedestrian network is an interconnected system of walkways, sidewalks, crossings, and paths designed to facilitate safe and efficient movement of people on foot within and between 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_69aed9569a4481908b6c1fcec2a11e21 |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:46 p.m.