Triple
T13945791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gila River Hotels & Casinos |
E335381
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | tribal gaming enterprise |
C15843
|
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: tribal gaming enterprise Context triple: [Gila River Hotels & Casinos, instanceOf, tribal gaming enterprise]
-
A.
tribally owned holding company
A tribally owned holding company is a business entity owned and controlled by a Native American tribe or tribal government that manages and oversees a portfolio of subsidiary enterprises to generate revenue, support economic development, and advance tribal sovereignty and community goals.
-
B.
gambling establishment
chosen
A gambling establishment is a venue where people participate in games of chance or skill for money or other stakes under regulated conditions.
-
C.
gambling company
A gambling company is a business entity that offers games of chance or wagering services, typically involving money or valuables, through physical venues, online platforms, or both, while operating under relevant regulatory and licensing frameworks.
-
D.
casino and resort operator
A casino and resort operator is a business entity that develops, owns, and manages integrated properties combining gambling facilities with lodging, dining, entertainment, and other leisure amenities.
-
E.
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.
- 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_69d81c6081b88190b53e317c3370c8fe |
completed | April 9, 2026, 9:38 p.m. |
Created at: April 9, 2026, 10:17 p.m.