Triple
T16348182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parks and Recreation Division |
E396988
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | state parks administration body |
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: state parks administration body Context triple: [Parks and Recreation Division, instanceOf, state parks administration body]
-
A.
state park system
A state park system is a coordinated network of publicly managed natural, cultural, and recreational areas within a state, established to conserve resources and provide outdoor recreation and education for the public.
-
B.
national park authority
A national park authority is a governmental or designated public body responsible for managing, protecting, and promoting the sustainable use and enjoyment of a country's national parks and their natural and cultural resources.
-
C.
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.
-
D.
state recreation site
A state recreation site is a designated public area managed by a state agency that provides natural or developed settings for outdoor leisure activities such as camping, hiking, fishing, and picnicking.
-
E.
park management headquarters
The park management headquarters is a central facility where administrative staff coordinate operations, planning, and resource management for one or more parks.
- 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_69d87f26864c819088365ca381a003c2 |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 10, 2026, 5:07 a.m.