Triple
T23925330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cardiff civic open spaces network |
E602334
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | civic open space network |
C11360
|
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: civic open space network Context triple: [Cardiff civic open spaces network, instanceOf, civic open space network]
-
A.
urban public space
An urban public space is a publicly accessible area within a city—such as streets, parks, plazas, and squares—designed or used for social interaction, movement, recreation, and civic life.
-
B.
civic precinct
A civic precinct is a designated urban area that concentrates key public institutions, government buildings, and community spaces to serve as a focal point for civic life and public services.
-
C.
urban park system component
chosen
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.
river valley park system
A river valley park system is an interconnected network of parks, trails, and natural areas along a river corridor designed to protect ecosystems, manage floodplains, and provide recreational and scenic opportunities for the public.
-
E.
riverside parklands
Riverside parklands are public green spaces located along riverbanks that provide recreational areas, natural habitat, and scenic corridors integrating water, vegetation, and human use.
- 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_69e2953b928c819095395fa87baca583 |
completed | April 17, 2026, 8:16 p.m. |
Created at: April 17, 2026, 8:42 p.m.