Triple
T17444926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Detroit Downtown Development Authority |
E424755
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | local development 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: local development authority Context triple: [Detroit Downtown Development Authority, instanceOf, local development authority]
-
A.
local council
A local council is a governing body elected or appointed to make decisions, set policies, and manage public services for a specific municipality or local area.
-
B.
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.
-
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.
local governmental entity
A local governmental entity is an administrative organization, such as a city, county, or district, that exercises governmental authority and provides public services within a specific geographic area below the level of the central or national government.
-
E.
metropolitan authority
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.
- 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_69d889db0ba481908402409af3b37917 |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:47 a.m.