Triple
T35870128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chicago Historic Bungalow Initiative |
E1037200
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | city-supported program |
C10627
|
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: city-supported program Context triple: [Chicago Historic Bungalow Initiative, instanceOf, city-supported program]
-
A.
community-based program
A community-based program is an organized set of activities and services designed and delivered within a local community to address shared needs, build capacity, and improve well-being through active resident participation and local partnerships.
-
B.
municipal program
chosen
A municipal program is an organized set of services, initiatives, or activities implemented and managed by a local government to address community needs and improve public welfare within its jurisdiction.
-
C.
community development program
A community development program is an organized initiative designed to improve the social, economic, and environmental well-being of a specific community through collaborative planning, resource mobilization, and capacity-building activities.
-
D.
New York City program
A New York City program is an organized, city-sanctioned initiative or service designed to address specific public needs or policy goals within the five boroughs.
-
E.
public housing subsidy program
A public housing subsidy program is a government initiative that provides financial assistance or reduced-cost housing to eligible low-income individuals and families to ensure access to safe, stable, and affordable homes.
- 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_69f76e1e701c8190a4990d4978ce4fe6 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:06 p.m.