Triple
T10400284
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Forbes Travel Guide Recommended ratings |
E245127
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | hospitality rating tier |
C9567
|
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 rating tier Context triple: [Forbes Travel Guide Recommended ratings, instanceOf, hospitality rating tier]
-
A.
hospitality rating
chosen
A hospitality rating is a quantified assessment that reflects the quality of service, comfort, and overall guest experience provided by a hospitality establishment such as a hotel or restaurant.
-
B.
hotel category
A hotel category represents a classification of hotels based on standardized criteria such as quality, amenities, service level, and price range to guide customer expectations and choices.
-
C.
restaurant classification
Restaurant classification is the conceptual process of categorizing dining establishments based on attributes such as cuisine type, price range, service style, ambiance, and location to support organization, recommendation, and analysis.
-
D.
Universal Orlando Resort hotel tier
A Universal Orlando Resort hotel tier categorizes on-site hotels into levels based on price, amenities, proximity to the parks, and included guest benefits such as Express Pass access and early park admission.
-
E.
Walt Disney World resort tier
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.
- 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_69d381b5116081908d85227bab6d3c0c |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 12:07 p.m.