Triple
T18286447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Region 5 |
E437996
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | administrative division of the U.S. Forest Service |
C15943
|
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: administrative division of the U.S. Forest Service Context triple: [Region 5, instanceOf, administrative division of the U.S. Forest Service]
-
A.
United States Forest Service region
chosen
A United States Forest Service region is a major administrative division of the USFS that oversees and coordinates the management of national forests, grasslands, and related resources within a specific multi-state geographic area.
-
B.
U.S. Forest Service ranger district
A U.S. Forest Service ranger district is a local administrative subdivision of a national forest, managed by a district ranger and staff who oversee land use, recreation, resource management, and conservation activities within its boundaries.
-
C.
U.S. Forest Service facility
A U.S. Forest Service facility is a government-operated site, such as ranger stations, visitor centers, research labs, or maintenance depots, that supports the management, conservation, and public use of national forests and grasslands.
-
D.
forestry division
A forestry division is an organizational unit within a government or company responsible for managing, conserving, and utilizing forest resources within a defined geographic area.
-
E.
forestry district
A forestry district is an administratively defined geographic area managed for the planning, regulation, and sustainable use of forest resources and related activities.
- 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_69d8b914530c8190b4474d862a2b2a1b |
completed | April 10, 2026, 8:47 a.m. |
Created at: April 10, 2026, 10:35 a.m.