Triple
T7688217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hamilton County Development Authority |
E174176
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | economic development authority |
C2948
|
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: economic development authority Context triple: [Hamilton County Development Authority, instanceOf, economic development authority]
-
A.
economic development agency
chosen
An economic development agency is an organization, typically public or public–private, that designs and implements programs to attract investment, support businesses, and promote sustainable economic growth within a specific region.
-
B.
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.
-
C.
economic and technological development zone
An economic and technological development zone is a designated area where governments concentrate infrastructure, incentives, and regulatory support to attract investment, foster industrial innovation, and accelerate regional economic growth.
-
D.
regional planning agency
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.
-
E.
regional development fund
A regional development fund is a financial mechanism that pools and allocates resources to support economic growth, infrastructure, and social development projects within a specific geographic area.
- 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_69c6995966348190939e6c37ba272c06 |
completed | March 27, 2026, 2:51 p.m. |
Created at: March 27, 2026, 4:02 p.m.