Triple
T12298558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zone 4 Bureau De Change cluster |
E293154
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | business district sub-area |
C526
|
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 sub-area Context triple: [Zone 4 Bureau De Change cluster, instanceOf, business district sub-area]
-
A.
urban business district
chosen
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.
-
B.
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.
-
C.
subregion of metropolitan area
A subregion of a metropolitan area is a geographically or functionally distinct part of a larger urban region, characterized by shared land use, demographics, infrastructure, or economic activity.
-
D.
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.
-
E.
road district
A road district is a defined administrative area responsible for the construction, maintenance, and management of public roads and related infrastructure within its boundaries.
- 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_69d6ab690ad081908c0ed3870ec82d53 |
completed | April 8, 2026, 7:24 p.m. |
Created at: April 8, 2026, 9:52 p.m.