Triple
T28360117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Territorial Forest Circles of Himachal Pradesh Forest Department |
E718340
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | forest administrative unit |
C23276
|
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: forest administrative unit Context triple: [Territorial Forest Circles of Himachal Pradesh Forest Department, instanceOf, forest administrative unit]
-
A.
forest preserve unit
A forest preserve unit is a designated tract of land managed for the protection, restoration, and sustainable use of forest ecosystems and their associated wildlife and recreational resources.
-
B.
forestry district
chosen
A forestry district is an administratively defined geographic area managed for the planning, regulation, and sustainable use of forest resources and related activities.
-
C.
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.
-
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.
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_69eff6ed5af48190be4e0adf298223e0 |
completed | April 27, 2026, 11:53 p.m. |
Created at: April 28, 2026, 12:51 a.m.