Triple
T7586688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Capitol Hill Parks reservations and circles |
E179629
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | urban park system unit |
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: urban park system unit Context triple: [Capitol Hill Parks reservations and circles, instanceOf, urban park system unit]
-
A.
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.
-
B.
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.
-
C.
urban planning unit
An urban planning unit is a defined spatial or administrative area within a city used as a basic building block for analyzing, designing, and regulating land use, infrastructure, and development policies.
-
D.
park system
A park system is an organized network of public parks and green spaces managed collectively to provide recreation, conservation, and aesthetic benefits to a community or region.
-
E.
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.
- 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_69c69f335248819093c1006f30513708 |
completed | March 27, 2026, 3:16 p.m. |
Created at: March 27, 2026, 3:52 p.m.