Triple
T22285244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cumberland Community Improvement District |
E550843
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | community improvement district |
C42151
|
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 improvement district Context triple: [Cumberland Community Improvement District, instanceOf, community improvement district]
-
A.
community plan area
A community plan area is a geographically defined section of a jurisdiction for which detailed land use, development, and infrastructure policies are established to guide local growth and community character.
-
B.
general improvement district
chosen
A general improvement district is a special-purpose local government entity created to finance, construct, operate, and maintain specific public improvements or services within a defined geographic area.
-
C.
neighborhood association
A neighborhood association is a community-based organization formed by residents of a specific area to address local issues, coordinate activities, and advocate for the neighborhood’s interests.
-
D.
business improvement district management organization
A business improvement district management organization is an entity, typically a nonprofit or quasi-public body, that administers and funds enhanced services and improvements within a defined commercial area using assessments collected from local property or business owners.
-
E.
community organisation
A community organisation is a structured group of people who collaborate locally to address shared needs, interests, or issues and to improve the well-being of their community.
- 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_69e11e44d538819097c6b8f333af3352 |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:40 p.m.