Triple
T15325680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kahnawà:ke Gaming Commission |
E366404
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | gaming regulatory authority |
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: gaming regulatory authority Context triple: [Kahnawà:ke Gaming Commission, instanceOf, gaming regulatory authority]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
gaming ecosystem
A gaming ecosystem is an interconnected network of platforms, hardware, software, communities, and services that collectively enable the creation, distribution, monetization, and play of video games.
-
E.
state regulatory agency
A state regulatory agency is a government body at the state level responsible for creating, implementing, and enforcing rules and standards within specific sectors (such as utilities, health, or finance) to protect the public interest and ensure legal 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_69d85a121520819093dcce999fdefe1a |
completed | April 10, 2026, 2:01 a.m. |
Created at: April 10, 2026, 3:16 a.m.