Triple
T19711815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | H2Ocio shopping centre |
E473367
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | commercial and leisure 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: commercial and leisure complex Context triple: [H2Ocio shopping centre, instanceOf, commercial and leisure complex]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
sports-oriented corporate complex
A sports-oriented corporate complex is a multi-use business facility that integrates office spaces with extensive athletic, fitness, and recreational amenities to promote employee wellness, team-building, and an active corporate culture.
-
E.
commercial park
A commercial park is a planned area of land developed with multiple business facilities—such as offices, retail spaces, and light industrial units—designed to support commercial activities within a cohesive, often landscaped 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_69d8e516dd048190a0b6c93ea3e71f58 |
completed | April 10, 2026, 11:55 a.m. |
Created at: April 10, 2026, 1:46 p.m.