Triple
T10636823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Torino World Design Capital projects |
E250603
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | urban design initiative |
C6939
|
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: urban design initiative Context triple: [Torino World Design Capital projects, instanceOf, urban design initiative]
-
A.
urban design project
chosen
An urban design project is a coordinated planning and design effort that shapes the physical form, public spaces, infrastructure, and land use of a specific urban area to improve its functionality, aesthetics, and livability.
-
B.
urban design movement
An urban design movement is a collective, often time-bound approach to shaping cities’ physical form, public spaces, and infrastructure based on shared social, cultural, environmental, and aesthetic principles.
-
C.
urban design department
The urban design department is a municipal or institutional unit responsible for planning, shaping, and regulating the physical form and public spaces of cities to create functional, attractive, and sustainable urban environments.
-
D.
urban development
Urban development is the planned growth and improvement of cities and towns through the design, regulation, and construction of buildings, infrastructure, and public spaces to support economic, social, and environmental needs.
-
E.
urban design element
An urban design element is a physical or spatial feature—such as streets, plazas, parks, or street furniture—that shapes the form, function, and experience 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_69d6aa5993448190a493b790b8f85010 |
completed | April 8, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:04 p.m.