Triple
T14090814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queen Wilhelmina State Park |
E339125
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Arkansas state park |
C34055
|
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: Arkansas state park Context triple: [Queen Wilhelmina State Park, instanceOf, Arkansas state park]
-
A.
Missouri state park
A Missouri state park is a protected natural or historic area within the state of Missouri that is managed by the Missouri Department of Natural Resources for public recreation, conservation, and education.
-
B.
Kentucky state park
A Kentucky state park is a designated natural or historic area within the state of Kentucky that is preserved, managed, and developed by the state for public recreation, conservation, and education.
-
C.
Oklahoma state park
An Oklahoma state park is a publicly managed natural or recreational area within the state of Oklahoma that preserves local landscapes, wildlife, and cultural resources while providing facilities and opportunities for outdoor activities such as camping, hiking, fishing, and picnicking.
-
D.
Pennsylvania state park
A Pennsylvania state park is a protected public area within the Commonwealth of Pennsylvania managed for conservation, recreation, and education, typically offering natural landscapes, wildlife habitats, and outdoor activities such as hiking, camping, and boating.
-
E.
Alaska state park
An Alaska state park is a designated natural or cultural area within the state of Alaska managed for public recreation, conservation, and the protection of wildlife and scenic resources.
- 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_69d81c687b0c819087fd9ed4198403f8 |
completed | April 9, 2026, 9:38 p.m. |
Created at: April 9, 2026, 10:21 p.m.