Triple
T7339671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West Virginia State Parks |
E169215
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | state park system |
C22019
|
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 park system Context triple: [West Virginia State Parks, instanceOf, state park system]
-
A.
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.
-
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.
national park area
A national park area is a protected geographic region designated by a government to conserve natural landscapes, ecosystems, and wildlife while providing opportunities for public recreation and education.
-
D.
New Jersey state park system unit
A New Jersey state park system unit is an individual protected area—such as a state park, forest, recreation area, historic site, or wildlife management area—administered by the state to conserve natural and cultural resources while providing public recreation and education.
-
E.
Oregon state park
An Oregon state park is a publicly managed natural or recreational area within the state of Oregon, preserved and maintained for conservation, outdoor activities, and public enjoyment.
- 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_69c68a57710481909f0c1f3c6ebdb6f2 |
completed | March 27, 2026, 1:47 p.m. |
Created at: March 27, 2026, 3:04 p.m.