Triple
T3987156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ahmedabad Urban Development Authority |
E86900
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | urban development authority |
C1090
|
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 development authority Context triple: [Ahmedabad Urban Development Authority, instanceOf, urban development authority]
-
A.
urban planning unit
An urban planning unit is a defined spatial or administrative area within a city used as a basic building block for analyzing, designing, and regulating land use, infrastructure, and development policies.
-
B.
urban development
Urban development is the planned growth and improvement of cities and towns through the design, regulation, and construction of buildings, infrastructure, and public spaces to support economic, social, and environmental needs.
-
C.
municipal agency
A municipal agency is a local government organization responsible for delivering specific public services, enforcing local regulations, and managing community programs within a city or town.
-
D.
occupation authority division
Occupation authority division is the organizational structure and allocation of powers among governing bodies or agencies responsible for administering and controlling a territory under military or foreign occupation.
-
E.
regional planning agency
chosen
A regional planning agency is an organization responsible for coordinating land use, transportation, infrastructure, and environmental planning across multiple jurisdictions within a defined geographic region.
- 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_69aed93fd9d4819085d3b2137d2346cb |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:33 p.m.