Triple
T17954090
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lutyens Bungalow Zone |
E448902
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | heritage zone |
C24185
|
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: heritage zone Context triple: [Lutyens Bungalow Zone, instanceOf, heritage zone]
-
A.
historical district
chosen
A historical district is a geographically defined area recognized for its concentration of buildings, structures, and sites that collectively reflect significant cultural, architectural, or historical heritage.
-
B.
heritage asset
A heritage asset is a building, monument, site, landscape, or object of historical, cultural, architectural, or archaeological significance that is preserved for its value to present and future generations.
-
C.
heritage centre
A heritage centre is a facility dedicated to preserving, interpreting, and presenting the historical, cultural, and natural heritage of a specific place or community for public education and engagement.
-
D.
archaeological district
An archaeological district is a geographically defined area containing a significant concentration, linkage, or continuity of archaeological sites, features, or artifacts that collectively represent important historical or prehistorical activities or cultures.
-
E.
architectural district
An architectural district is a geographically defined area characterized by a concentration of buildings and structures that share significant architectural styles, historical periods, or design features, often protected or managed for their cultural and aesthetic value.
- 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_69d8b9f8cca8819099836916c56b7c95 |
completed | April 10, 2026, 8:51 a.m. |
Created at: April 10, 2026, 10:21 a.m.