Triple
T36892181
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Downtown Redevelopment Authority |
E911776
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | redevelopment authority |
C23517
|
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: redevelopment authority Context triple: [Downtown Redevelopment Authority, instanceOf, redevelopment 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.
urban renewal agency
An urban renewal agency is a public or quasi-public organization responsible for planning, coordinating, and implementing projects to revitalize and redevelop blighted or underutilized urban areas.
-
C.
development authority
chosen
A development authority is an organization or governmental body responsible for planning, regulating, and facilitating land use, infrastructure, and urban or regional development within a designated area.
-
D.
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.
-
E.
station redevelopment organization
A station redevelopment organization is an entity responsible for planning, coordinating, and executing the modernization and transformation of railway or transit stations to improve functionality, accessibility, and surrounding urban environments.
- 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_69f76e8335908190b77e7e11d0e80820 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:13 p.m.