Triple
T11851615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jaipur Walled City |
E281921
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | planned city quarter |
C6632
|
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: planned city quarter Context triple: [Jaipur Walled City, instanceOf, planned city quarter]
-
A.
planned city
A planned city is an urban area whose layout, infrastructure, and land use are deliberately designed and constructed according to a comprehensive plan before significant settlement occurs.
-
B.
planned commercial district
A planned commercial district is a deliberately designed area designated for concentrated business, retail, and service activities, typically guided by zoning regulations and urban planning principles to support economic activity and accessibility.
-
C.
European-planned district
A European-planned district is an urban area deliberately designed and laid out according to European planning principles, often featuring organized street grids or boulevards, designated civic and commercial zones, and architectural styles reflecting European influence.
-
D.
part of city
chosen
A part of city is a spatially bounded urban area, such as a neighborhood or district, characterized by specific physical, social, or functional attributes within the larger city.
-
E.
fortified quarter
A fortified quarter is a heavily defended district within a settlement, protected by walls, towers, and controlled access points to safeguard key populations, resources, or institutions.
- 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_69d6ab287ba48190a5178779fd19b9b7 |
completed | April 8, 2026, 7:23 p.m. |
Created at: April 8, 2026, 9:43 p.m.