Triple
T15240865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UK Gambling Commission |
E364250
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | gambling regulator |
C1181
|
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: gambling regulator Context triple: [UK Gambling Commission, instanceOf, gambling regulator]
-
A.
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.
-
B.
gambling establishment
A gambling establishment is a venue where people participate in games of chance or skill for money or other stakes under regulated conditions.
-
C.
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.
-
D.
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.
-
E.
regulatory authority
chosen
A regulatory authority is an official body empowered by law to create, implement, and enforce rules and standards within a specific domain to protect public interests and ensure compliance.
- 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_69d85a0dde7481908fc64d1e82d5d20d |
completed | April 10, 2026, 2:01 a.m. |
Created at: April 10, 2026, 3:13 a.m.