Triple
T28136436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rank Hotels |
E714218
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | hospitality division |
C54444
|
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: hospitality division Context triple: [Rank Hotels, instanceOf, hospitality division]
-
A.
hospitality design division
A hospitality design division is a specialized team or department that plans, designs, and oversees the creation of guest-focused environments such as hotels, resorts, and restaurants to enhance user experience and brand identity.
-
B.
hospitality service
A hospitality service is a business or offering that provides lodging, food, beverages, and related amenities to guests, focusing on comfort, convenience, and positive customer experiences.
-
C.
hospitality brand
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.
-
D.
hospitality venue
A hospitality venue is a place that provides guests with lodging, food, beverages, and/or entertainment services in a welcoming, service-oriented environment.
-
E.
hospitality industry event
A hospitality industry event is a planned gathering where professionals from hotels, restaurants, travel, and related services meet to network, showcase offerings, share industry insights, and explore business opportunities.
- 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_69efd6af156c81908f50c2cd7db0e1ef |
completed | April 27, 2026, 9:35 p.m. |
Created at: April 27, 2026, 9:50 p.m.