Triple

T7883024
Position Surface form Disambiguated ID Type / Status
Subject National Cohesive Wildland Fire Management Strategy E183029 entity
Predicate instanceOf P0 FINISHED
Object wildland fire management strategy C15309 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: wildland fire management strategy
Context triple: [National Cohesive Wildland Fire Management Strategy, instanceOf, wildland fire management strategy]
  • A. 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.
  • B. 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.
  • C. forest management program
    A forest management program is an organized set of policies, practices, and monitoring activities designed to sustainably manage forest resources, balance ecological health with economic and social needs, and ensure long-term forest resilience.
  • D. ecosystem management plan chosen
    An ecosystem management plan is a strategic, science-based framework that outlines goals, actions, and monitoring methods to maintain or restore the health, resilience, and sustainability of a specific ecosystem while balancing ecological, social, and economic needs.
  • E. wildlife management area
    A wildlife management area is a designated tract of land or water managed primarily for the conservation, habitat protection, and regulated use of wildlife and natural resources.
  • 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_69ca828af6e48190a06ee7010d8f0e64 completed March 30, 2026, 2:02 p.m.
Created at: March 30, 2026, 4:58 p.m.