Triple
T27727762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hyperion Lounge |
E697348
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Disney hotel restaurant |
C53210
|
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: Disney hotel restaurant Context triple: [Hyperion Lounge, instanceOf, Disney hotel restaurant]
-
A.
Disneyland Paris hotel
A Disneyland Paris hotel is a themed accommodation located within or near the Disneyland Paris resort, offering immersive Disney experiences, park proximity, and exclusive guest benefits.
-
B.
Tokyo Disney Resort hotel
A Tokyo Disney Resort hotel is an accommodation facility located within or near Tokyo Disney Resort that offers themed lodging, dining, and services tailored to guests visiting the resort’s parks and entertainment areas.
-
C.
Disney Vacation Club resort
A Disney Vacation Club resort is a themed, Disney-owned vacation property where members use points-based timeshare ownership to book accommodations and enjoy on-site and nearby Disney amenities.
-
D.
Disneyland Paris partner hotel
A Disneyland Paris partner hotel is an officially affiliated accommodation located near the resort that offers themed stays, convenient access, and select Disney-related benefits without being directly inside the Disney-owned hotel portfolio.
-
E.
Disney resort complex
A Disney resort complex is a large, themed vacation destination that combines multiple hotels, entertainment venues, dining, shopping, and recreational facilities centered around Disney parks and experiences.
- F. None of above. chosen
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_69ef590c3e288190ad54d2465af8ca4e |
completed | April 27, 2026, 12:39 p.m. |
Created at: April 27, 2026, 3:10 p.m.