Triple
T33836016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maine Gambling Control Unit |
E867236
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | gambling regulatory authority |
C2929
|
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 regulatory authority Context triple: [Maine Gambling Control Unit, instanceOf, gambling regulatory authority]
-
A.
regulatory authority
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.
financial regulatory authority
A financial regulatory authority is an organization empowered by law to oversee, supervise, and enforce rules governing financial markets and institutions to ensure stability, integrity, and consumer protection.
-
C.
state regulatory agency
chosen
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.
-
D.
alcoholic beverage control authority
An alcoholic beverage control authority is a governmental or regulatory body responsible for licensing, monitoring, and enforcing laws related to the production, distribution, sale, and consumption of alcoholic beverages within its jurisdiction.
-
E.
horse racing authority
A horse racing authority is an organization responsible for regulating, overseeing, and enforcing rules and standards for horse racing within a specific jurisdiction.
- 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_69f34992ad40819087760ed939bd2a7a |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:47 a.m.