Triple
T2667952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MGM Grand (licensing of brand to casinos and hotels) |
E55682
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | hospitality and gaming brand |
C7188
|
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 and gaming brand Context triple: [MGM Grand (licensing of brand to casinos and hotels), instanceOf, hospitality and gaming brand]
-
A.
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.
-
B.
hotel and casino
A hotel and casino is an establishment that combines lodging accommodations with on-site gambling facilities, often supplemented by dining, entertainment, and leisure amenities.
-
C.
casino brand
chosen
A casino brand is a distinct identity that represents a gambling establishment or network, encompassing its name, visual style, reputation, and overall customer experience across physical and/or digital venues.
-
D.
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.
-
E.
casino magnate
A casino magnate is a powerful business figure who owns, develops, or controls major gambling and entertainment properties, shaping the casino industry through large-scale investments and strategic influence.
- 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_69ab49e54de48190be708cd1cf8be073 |
completed | March 6, 2026, 9:40 p.m. |
Created at: March 6, 2026, 9:54 p.m.