Triple
T31321303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holiday Inn Club Vacations |
E798748
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | vacation ownership brand |
C16759
|
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: vacation ownership brand Context triple: [Holiday Inn Club Vacations, instanceOf, vacation ownership brand]
-
A.
vacation ownership program
chosen
A vacation ownership program is a structured arrangement, often involving timeshares or points-based systems, that allows individuals to pre-purchase the right to use accommodations or travel services at specific resorts or destinations over a set period or on a recurring basis.
-
B.
destination brand
A destination brand is the unique identity, image, and set of associations created to distinguish a place (such as a city, region, or country) in the minds of target audiences, influencing their perceptions and travel or investment decisions.
-
C.
vacation add-on
A vacation add-on is an optional, supplementary product or service—such as excursions, insurance, upgrades, or special experiences—purchased in addition to a core travel booking to enhance or personalize a trip.
-
D.
resort
A resort is a commercial establishment that provides lodging, dining, recreation, and leisure amenities in a single destination designed for relaxation and vacation experiences.
-
E.
value resort
A value resort is a budget-friendly vacation property that offers essential amenities and comfortable accommodations at lower prices than traditional resorts, often with fewer luxury features but convenient access to key attractions.
- 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_69f224e3238c8190b2291f50ea4962cd |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 9:15 p.m.