Triple
T7551066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UNESCO World Heritage buffer boundary |
E178534
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | spatial planning instrument |
C22869
|
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: spatial planning instrument Context triple: [UNESCO World Heritage buffer boundary, instanceOf, spatial planning instrument]
-
A.
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.
-
B.
land use plan
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.
-
C.
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.
-
D.
regional planning program
A regional planning program is an organized framework of policies, strategies, and actions designed to guide the coordinated development, land use, infrastructure, and resource management of a specific geographic area over time.
-
E.
town planning policy
Town planning policy is a set of rules and guidelines that shape how land is used and developed in a town to balance social, economic, and environmental needs.
- 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_69c69f2cbe08819088f9eb0c03ef529b |
completed | March 27, 2026, 3:15 p.m. |
Created at: March 27, 2026, 3:49 p.m.