Triple
T15706656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henry Parkes Centre |
E380728
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cultural and tourism complex |
C10870
|
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: cultural and tourism complex Context triple: [Henry Parkes Centre, instanceOf, cultural and tourism complex]
-
A.
entertainment complex
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 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.
monumental complex
A monumental complex is a large-scale, architecturally unified grouping of significant structures and spaces—such as temples, palaces, plazas, or memorials—designed to serve major ceremonial, political, religious, or commemorative functions.
-
D.
cultural theme park
A cultural theme park is a recreational venue that immerses visitors in the traditions, history, arts, and lifestyles of one or more cultures through themed environments, performances, exhibits, and activities.
-
E.
tourist facility
chosen
A tourist facility is a place or establishment that provides services, amenities, or attractions specifically designed to accommodate and enhance the experience of visitors and travelers.
- 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_69d86d9bf930819082b30cf6d169297c |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:45 a.m.