Triple
T33114713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gateway Casinos & Entertainment |
E847427
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | gaming and entertainment company |
C32310
|
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 and entertainment company Context triple: [Gateway Casinos & Entertainment, instanceOf, gaming and entertainment company]
-
A.
leisure and entertainment company
chosen
A leisure and entertainment company is an organization that creates, manages, and delivers recreational, cultural, and amusement experiences to consumers through venues, events, media, or activities designed for enjoyment and relaxation.
-
B.
video game technology company
A video game technology company is an organization that develops and provides software, hardware, tools, or platforms that enable the creation, optimization, and distribution of interactive digital games.
-
C.
sports and entertainment company
A sports and entertainment company is an organization that creates, manages, and promotes athletic competitions, live events, media content, and related experiences for audiences and fans.
-
D.
social gaming company
A social gaming company is an organization that develops and operates games designed to be played and shared with others, emphasizing online interaction, community features, and social engagement among players.
-
E.
video game development company
A video game development company is an organization that designs, creates, tests, and publishes interactive digital games for various platforms such as consoles, PCs, and mobile devices.
- 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_69f3495751a081909850af5843da40dc |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:27 a.m.