Triple
T29186858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yamuna Biodiversity Park (near floodplain zone) |
E739891
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | urban ecological reserve |
C7244
|
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: urban ecological reserve Context triple: [Yamuna Biodiversity Park (near floodplain zone), instanceOf, urban ecological reserve]
-
A.
urban conservation area
chosen
An urban conservation area is a designated part of a city where the historic, architectural, and environmental character is protected and managed through specific planning and development controls.
-
B.
urban park
An urban park is a publicly accessible green space within a city that provides recreational areas, natural scenery, and social gathering places for residents and visitors.
-
C.
urban state park
An urban state park is a publicly managed natural or recreational area located within or adjacent to a city, providing green space, outdoor activities, and conservation of local ecosystems for urban residents and visitors.
-
D.
urban environmental complex
An urban environmental complex is an integrated system of natural and built elements within a city—such as green spaces, water bodies, infrastructure, and human activities—that interact to shape the urban ecosystem’s ecological, social, and climatic conditions.
-
E.
urban enclosure
An urban enclosure is a defined spatial area within a city—such as a courtyard, plaza, or block—whose physical and social boundaries create a sense of contained, cohesive public or semi-public environment.
- 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_69f07cb74c2c8190ad396487fcb4fde6 |
completed | April 28, 2026, 9:24 a.m. |
Created at: April 28, 2026, noon