Triple
T22496569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harriet Tubman Underground Railroad State Park |
E556156
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Maryland state park |
C40619
|
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: Maryland state park Context triple: [Harriet Tubman Underground Railroad State Park, instanceOf, Maryland state park]
-
A.
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.
-
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.
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.
-
D.
Arkansas state park
An Arkansas state park is a protected natural, cultural, or recreational area within the state of Arkansas that is managed by the state government for public enjoyment, education, and conservation.
-
E.
state park in the United States
chosen
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.
- 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_69e11e5445bc8190b6a9481926db3355 |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:50 p.m.