Triple
T28499573
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ashton Moss area |
E721196
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | commercial and leisure district |
C31058
|
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: commercial and leisure district Context triple: [Ashton Moss area, instanceOf, commercial and leisure district]
-
A.
planned commercial district
A planned commercial district is a deliberately designed area designated for concentrated business, retail, and service activities, typically guided by zoning regulations and urban planning principles to support economic activity and accessibility.
-
B.
Commercial area
chosen
A commercial area is a designated zone within a city or region primarily used for business activities such as retail, offices, services, and entertainment.
-
C.
pedestrian-oriented commercial district
A pedestrian-oriented commercial district is a compact, walkable area where shops, services, and public spaces are clustered and designed primarily for people on foot rather than for automobile access.
-
D.
commercial and residential complex
A commercial and residential complex is a mixed-use development that integrates living spaces with retail, office, and service facilities within a unified property or group of buildings.
-
E.
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.
- 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_69f01a5afdac8190ac6e72d5c100bd58 |
completed | April 28, 2026, 2:24 a.m. |
Created at: April 28, 2026, 3:06 a.m.