Triple
T31305291
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northeast D.C. commercial network |
E798319
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | business district cluster |
C30938
|
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: business district cluster Context triple: [Northeast D.C. commercial network, instanceOf, business district cluster]
-
A.
group of central business districts
chosen
A group of central business districts is a collection of geographically distinct urban cores where commercial, financial, and administrative activities are highly concentrated and functionally interconnected.
-
B.
urban business district
An urban business district is a densely developed area within a city characterized by a high concentration of offices, commercial activities, financial institutions, and supporting services that form the economic core of the urban environment.
-
C.
Commercial area
A commercial area is a designated zone within a city or region primarily used for business activities such as retail, offices, services, and entertainment.
-
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.
industrial district
An industrial district is a designated urban or regional area characterized by a high concentration of manufacturing, warehousing, and related industrial activities supported by specialized infrastructure and services.
- 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_69f224e0bd4c8190aab9b29a73f7aa3c |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 9:14 p.m.