Triple
T10681032
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Disney’s BoardWalk entertainment district |
E251755
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | shopping and dining district |
C13800
|
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 and dining district Context triple: [Disney’s BoardWalk entertainment district, instanceOf, shopping and dining district]
-
A.
entertainment district
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.
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.
-
C.
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.
-
D.
shopping area
chosen
A shopping area is a designated space, such as a street, district, or complex, where multiple retail stores and related services are concentrated for consumer purchasing and leisure activities.
-
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_69d6aa5bd7c08190a816e733b4045c23 |
completed | April 8, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:10 p.m.