Triple
T22007425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hollofield Area |
E543485
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | developed area of a state park |
C21075
|
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: developed area of a state park Context triple: [Hollofield Area, instanceOf, developed area of a state park]
-
A.
facility in a national park
A facility in a national park is a built or managed structure, area, or service (such as visitor centers, campgrounds, restrooms, or trails) provided to support recreation, education, conservation, and visitor safety within the park.
-
B.
entrance to a national park
The entrance to a national park is the designated access point where visitors transition from surrounding areas into the protected natural landscape, often marked by signage, gates, and visitor facilities.
-
C.
state park in the United States
A state park in the United States is a protected natural or recreational area managed by a state government, designated for conservation, outdoor activities, and public enjoyment.
-
D.
protected landscape area
A protected landscape area is a designated region where the interaction of people and nature over time has produced a distinct character with significant ecological, cultural, and scenic value that is conserved and managed through legal or other effective means.
-
E.
public recreational area
chosen
A public recreational area is a shared outdoor or indoor space designed and maintained for community use, providing facilities and environments for leisure, exercise, social interaction, and relaxation.
- 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_69e11e2db934819095556760c7d85e4d |
completed | April 16, 2026, 5:36 p.m. |
Created at: April 16, 2026, 8:21 p.m.