Triple
T28516049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VGTM-UDA |
E721621
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Urban development authority |
C16436
|
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: [VGTM-UDA, instanceOf, Urban development authority]
-
A.
urban-rural development authority
An urban-rural development authority is a governing body responsible for planning, coordinating, and regulating balanced infrastructure, land use, and economic development across both urban and rural areas within its jurisdiction.
-
B.
metropolitan authority
chosen
A metropolitan authority is a governing body responsible for planning, coordinating, and managing public services and development across a large urban area and its surrounding municipalities.
-
C.
Mayoral development corporation
A mayoral development corporation is a public body established by a city’s mayor to lead and coordinate regeneration, planning, and economic development within a designated urban area.
-
D.
urban planning department
An urban planning department is a governmental or organizational unit responsible for designing, regulating, and guiding the development and use of land, infrastructure, and public spaces within a city or metropolitan area.
-
E.
urban development company
An urban development company is an organization that plans, finances, and executes projects to design, build, and revitalize city spaces, infrastructure, and real estate in alignment with economic, social, and environmental goals.
- 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_69f01a5cbcc4819083fb4e723378713e |
completed | April 28, 2026, 2:24 a.m. |
Created at: April 28, 2026, 3:17 a.m.