Triple
T9327474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holiday Inn |
E224427
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | hospitality company brand |
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: hospitality company brand Context triple: [Holiday Inn, instanceOf, hospitality company brand]
-
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.
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.
-
C.
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.
-
D.
carrier hotel
A carrier hotel is a secure, high-connectivity data center facility where multiple telecommunications carriers, internet service providers, and network operators colocate equipment to interconnect and exchange traffic.
-
E.
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.
- 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_69ca8427a0c08190b749831d5ea98f02 |
completed | March 30, 2026, 2:09 p.m. |
Created at: March 30, 2026, 7:39 p.m.