Triple

T7715881
Position Surface form Disambiguated ID Type / Status
Subject Adirondack Park State Land Master Plan E174879 entity
Predicate instanceOf P0 FINISHED
Object land use management plan C15975 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: land use management plan
Context triple: [Adirondack Park State Land Master Plan, instanceOf, land use management plan]
  • A. land use plan chosen
    A land use plan is a strategic document that guides the allocation, development, and conservation of land within a defined area to balance environmental, social, and economic objectives.
  • B. land use planning area
    A land use planning area is a defined geographic region designated for coordinated management and regulation of land uses to achieve specific environmental, social, and economic development objectives.
  • C. land-use control
    Land-use control is the set of legal and administrative mechanisms by which governments and authorities regulate how land may be developed, used, and conserved within a given jurisdiction.
  • D. ecosystem management plan
    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. local and regional planning framework
    A local and regional planning framework is a structured set of policies, processes, and tools that guide coordinated land use, infrastructure, and development decisions across municipalities and regions to achieve sustainable, equitable, and efficient growth.
  • 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_69c6995c463c8190a14458036249d419 completed March 27, 2026, 2:51 p.m.
Created at: March 27, 2026, 4:04 p.m.