Triple
T17958979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Green Belt (Auroville) |
E449025
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | sustainable land-use zone |
C40213
|
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: sustainable land-use zone Context triple: [Green Belt (Auroville), instanceOf, sustainable land-use zone]
-
A.
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.
-
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 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.
public reserved land
Public reserved land is a designated area owned or controlled by a government entity and legally set aside for specific public purposes such as conservation, recreation, infrastructure, or future community use, restricting private development and exploitation.
-
E.
land use case
A land use case is a specific scenario or application that illustrates how a particular area of land is designated, managed, and regulated for activities such as residential, commercial, agricultural, industrial, or recreational purposes.
- 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_69d8b9f8cca8819099836916c56b7c95 |
completed | April 10, 2026, 8:51 a.m. |
Created at: April 10, 2026, 10:22 a.m.