Triple
T7325853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kansas City parks system |
E168873
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | municipal parks and recreation system |
C3341
|
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: municipal parks and recreation system Context triple: [Kansas City parks system, instanceOf, municipal parks and recreation system]
-
A.
parks and recreation agency
chosen
A parks and recreation agency is a public or private organization responsible for planning, managing, and providing recreational facilities, programs, and green spaces to enhance community well-being and environmental stewardship.
-
B.
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.
-
C.
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.
-
D.
community park
A community park is a public outdoor space designed to provide local residents with areas for recreation, relaxation, social interaction, and connection with nature.
-
E.
municipal property
Municipal property is any land, buildings, infrastructure, or other assets owned, leased, or otherwise controlled by a local government for public use or municipal operations.
- 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_69c68a54cacc81908e3b773441f19566 |
completed | March 27, 2026, 1:47 p.m. |
Created at: March 27, 2026, 3:03 p.m.