Triple
T19707275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Ritz-Carlton portfolio |
E473250
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | luxury hospitality brand portfolio |
C1963
|
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: luxury hospitality brand portfolio Context triple: [The Ritz-Carlton portfolio, instanceOf, luxury hospitality brand portfolio]
-
A.
hospitality brand
chosen
A hospitality brand is a distinctive identity that represents a company’s promise, values, and guest experience across its hotels, resorts, or related services in the travel and lodging industry.
-
B.
luxury hotel
A luxury hotel is a high-end lodging establishment that offers premium accommodations, personalized services, and upscale amenities designed to provide guests with exceptional comfort and exclusivity.
-
C.
luxury collection
A luxury collection is a curated assortment of high-end, premium products or experiences distinguished by exceptional quality, exclusivity, and sophisticated design.
-
D.
luxury brand
A luxury brand is a high-end label that offers premium products or services distinguished by exceptional quality, exclusivity, and a prestigious image that commands elevated prices.
-
E.
hotel consortium
A hotel consortium is an alliance of independently owned hotels that collaborate under a shared brand or network to leverage collective marketing, distribution, purchasing, and standards while retaining individual ownership and management.
- 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_69d8e516dd048190a0b6c93ea3e71f58 |
completed | April 10, 2026, 11:55 a.m. |
Created at: April 10, 2026, 1:46 p.m.