Triple
T32781012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Disney’s Yacht and Beach Club Resorts |
E838355
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Disney resort hotel complex |
C11673
|
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 resort hotel complex Context triple: [Disney’s Yacht and Beach Club Resorts, instanceOf, Disney resort hotel complex]
-
A.
Disney resort complex
chosen
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.
-
B.
Disneyland Resort facility
A Disneyland Resort facility is any physical location, structure, or venue within the Disneyland Resort that supports guest experiences, operations, entertainment, lodging, dining, or services.
-
C.
Disney establishment
A Disney establishment is any physical or virtual venue, facility, or location owned, operated, licensed, or branded by The Walt Disney Company that provides entertainment, retail, hospitality, or related services.
-
D.
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.
-
E.
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.
- 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_69f3493b83f48190be335cd42465cecf |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:14 a.m.