Triple
T34868830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oban Division |
E1005093
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | division of national park |
C62563
|
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: division of national park Context triple: [Oban Division, instanceOf, division of national park]
-
A.
division of the United States Park Police
A division of the United States Park Police is an organizational unit within the agency responsible for law enforcement, public safety, and resource protection in a specific geographic area or functional domain of the national park system.
-
B.
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.
-
C.
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.
-
D.
national government park
A national government park is a protected public area managed by a national authority to conserve natural or cultural resources while providing recreational and educational opportunities for visitors.
-
E.
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.
- 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_69f76dbb678081909a247b9b5e1a73ac |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4 p.m.