Triple
T37133383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bronx Community Districts |
E919587
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | community district system |
C66523
|
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: community district system Context triple: [Bronx Community Districts, instanceOf, community district system]
-
A.
community development district
A community development district is a special-purpose local government entity created to plan, finance, construct, operate, and maintain infrastructure and services for a specific community or development area.
-
B.
public facilities district
A public facilities district is a special-purpose governmental entity created to finance, develop, own, and operate public venues or infrastructure such as stadiums, convention centers, or cultural facilities, typically funded through dedicated taxes or fees.
-
C.
library district
A library district is a defined geographic area governed by a dedicated public entity that funds, manages, and provides library services to the residents within its boundaries.
-
D.
public utility district
A public utility district is a community-owned, special-purpose governmental entity that provides essential services such as electricity, water, or sewer to residents within a defined geographic area.
-
E.
metropolitan district
A metropolitan district is an administrative or governmental region that encompasses a central city and its surrounding urban and suburban areas, managed as a single integrated unit for planning, services, and governance.
- F. None of above. chosen
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_69f76e9d13e48190a108f7fbf80ff375 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:15 p.m.