Triple
T25888248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London District |
E652253
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ranger district of a national forest |
C13042
|
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: ranger district of a national forest Context triple: [London District, instanceOf, ranger district of a national forest]
-
A.
U.S. Forest Service ranger district
chosen
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.
-
B.
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.
-
C.
United States Forest Service region
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.
-
D.
part of a national forest
A part of a national forest is a designated subsection of federally protected woodland and associated ecosystems managed for conservation, recreation, and resource use within the larger national forest boundary.
-
E.
forest preserve district
A forest preserve district is a governmental or quasi-governmental entity responsible for acquiring, managing, and protecting natural areas and open space—often forests, prairies, wetlands, and related habitats—for conservation, recreation, and education.
- 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_69e7ab3b92cc81908febd90317862647 |
completed | April 21, 2026, 4:52 p.m. |
Created at: April 22, 2026, 8:18 a.m.