Triple
T5541713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | City of Pittsburgh park system |
E145304
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public park system |
C9179
|
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: public park system Context triple: [City of Pittsburgh park system, instanceOf, public park system]
-
A.
park system
chosen
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.
-
B.
park feature
A park feature is any designed or natural element within a park—such as paths, benches, playgrounds, gardens, or water bodies—that contributes to its use, aesthetics, or ecological value.
-
C.
park complex
A park complex is a large, planned outdoor area that combines multiple recreational, natural, and community facilities—such as playgrounds, sports fields, gardens, and walking paths—into a unified public space.
-
D.
deck park
A deck park is an elevated public green space constructed over transportation infrastructure, such as highways or rail lines, to reconnect urban areas and provide recreational and environmental benefits.
-
E.
park district
A park district is a local governmental or administrative entity responsible for planning, developing, maintaining, and operating public parks, recreational facilities, and related community programs within a defined geographic area.
- 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_69c008fa64888190adae56c8f9ea4031 |
completed | March 22, 2026, 3:21 p.m. |
Created at: March 22, 2026, 3:35 p.m.