Triple
T22190995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guilford Battle Ground Company park |
E548423
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | privately managed park |
C45921
|
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: privately managed park Context triple: [Guilford Battle Ground Company park, instanceOf, privately managed park]
-
A.
co-managed protected area
A co-managed protected area is a conservation zone where responsibility and authority for managing natural resources and biodiversity are shared between government agencies and local communities or other stakeholders through formal agreements.
-
B.
privately owned public space
A privately owned public space is an area of land or a building that is owned and managed by a private entity but legally required or designated to be accessible for public use.
-
C.
park conservancy
A park conservancy is a nonprofit or community-based organization dedicated to preserving, maintaining, and enhancing public parks and green spaces through stewardship, fundraising, and advocacy.
-
D.
park unit
A park unit is a designated area of land or water managed as a distinct entity within a larger park system for conservation, recreation, and public enjoyment.
-
E.
quasi-national park
A quasi-national park is a protected natural area designated and managed by regional or local authorities, offering conservation and recreation functions similar to a national park but with a lower or more flexible legal status.
- F. None of above. chosen
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_69e11e3e0c7c8190b30d278845e2497e |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:35 p.m.