Triple
T34918643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Three Rivers Greenway |
E1007075
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | urban park and trail system |
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 and trail system Context triple: [Three Rivers Greenway, instanceOf, urban park and trail system]
-
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 state park
An urban state park is a publicly managed natural or recreational area located within or adjacent to a city, providing green space, outdoor activities, and conservation of local ecosystems for urban residents and visitors.
-
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.
recreation trail
A recreation trail is a designated path or route intended for non-motorized leisure activities such as walking, hiking, cycling, or horseback riding, often located in natural or scenic 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_69f76dc2b6b0819095a61debbd405269 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4 p.m.