Triple
T25336954
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | California’s State Responsibility Area wildlands |
E635302
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fire management jurisdiction |
C50040
|
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: fire management jurisdiction Context triple: [California’s State Responsibility Area wildlands, instanceOf, fire management jurisdiction]
-
A.
forest administration role
A forest administration role is a position responsible for planning, regulating, and overseeing the sustainable management, protection, and use of forest resources within a defined jurisdiction.
-
B.
forest fire
A forest fire is an uncontrolled, rapidly spreading combustion in a woodland area that consumes vegetation and can threaten wildlife, human life, and property.
-
C.
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.
-
D.
wildfire-affected area
A wildfire-affected area is a geographic region that has experienced recent or ongoing wildfire activity, resulting in altered vegetation, soil conditions, and ecological or infrastructural impacts.
-
E.
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.
- 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_69e75a99bd6481909476115b35b9a8e4 |
completed | April 21, 2026, 11:08 a.m. |
Created at: April 21, 2026, 1:32 p.m.