Triple
T2904816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Downtown Disney District |
E62737
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | shopping, dining, and entertainment district |
C1309
|
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: shopping, dining, and entertainment district Context triple: [Downtown Disney District, instanceOf, shopping, dining, and entertainment district]
-
A.
entertainment district
chosen
An entertainment district is a designated urban area concentrated with venues such as theaters, bars, clubs, restaurants, and other leisure attractions that cater to nightlife and recreational activities.
-
B.
tourist district
A tourist district is a designated urban or regional area characterized by a high concentration of attractions, services, and infrastructure tailored to visitors, such as hotels, restaurants, shops, and cultural or entertainment venues.
-
C.
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.
-
D.
urban plaza
An urban plaza is a publicly accessible open space within a city, typically surrounded by buildings and streets, designed to support social interaction, circulation, and civic activities.
-
E.
shopping street
A shopping street is a public thoroughfare lined with a variety of retail stores, services, and eateries designed for pedestrian access and commercial activity.
- 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_69ab4c3e070c8190b78d3d2c005876dd |
completed | March 6, 2026, 9:50 p.m. |
Created at: March 6, 2026, 10:11 p.m.