Triple
T10988734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Value Resort Hotels |
E259701
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Disney resort hotel category |
C16749
|
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 category Context triple: [Value Resort Hotels, instanceOf, Disney resort hotel category]
-
A.
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.
-
B.
Walt Disney World resort tier
chosen
A Walt Disney World resort tier represents a classification level (such as Value, Moderate, Deluxe, or Deluxe Villa) that groups on-property hotels by price range, amenities, and overall guest experience.
-
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.
Walt Disney World Resort offering
A Walt Disney World Resort offering is any product, service, or experience—such as accommodations, theme park access, dining, entertainment, or vacation packages—provided under the Walt Disney World Resort brand to enhance guests’ visits.
-
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_69d6aa8a6a548190a750f944ccdc8064 |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:24 p.m.