Triple
T11196413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Expo City (entertainment and shopping complex) |
E264933
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | entertainment and shopping complex |
C725
|
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: entertainment and shopping complex Context triple: [Expo City (entertainment and shopping complex), instanceOf, entertainment and shopping complex]
-
A.
entertainment complex
chosen
An entertainment complex is a large, multi-purpose facility that combines various leisure, recreational, and cultural attractions—such as cinemas, theaters, restaurants, gaming areas, and event spaces—within a single integrated venue.
-
B.
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.
-
C.
shopping centre
A shopping centre is a large complex of retail stores, services, and often entertainment facilities planned and managed as a single commercial property.
-
D.
commercial and transportation complex
A commercial and transportation complex is a multifunctional facility that integrates retail, business services, and transit infrastructure to support shopping, commerce, and the movement of people and goods.
-
E.
entertainment facility
An entertainment facility is a venue designed and equipped to provide recreational, cultural, or leisure activities to individuals or groups, such as theaters, amusement parks, sports arenas, or gaming centers.
- 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_69d6aa9eb9248190b20211772621b4bc |
completed | April 8, 2026, 7:21 p.m. |
Created at: April 8, 2026, 9:29 p.m.