Triple
T20345907
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | eUniverse |
E495868
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | online entertainment company |
C18735
|
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: online entertainment company Context triple: [eUniverse, instanceOf, online entertainment company]
-
A.
leisure and entertainment company
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.
entertainment holding company
An entertainment holding company is a parent corporation that owns and manages controlling interests in multiple entertainment-related businesses, such as film studios, music labels, streaming platforms, and live event producers, to coordinate strategy and maximize overall value.
-
C.
multimedia company
chosen
A multimedia company is an organization that creates, produces, and distributes content across multiple media formats—such as video, audio, text, and interactive platforms—to inform, entertain, or engage audiences.
-
D.
online gaming company
An online gaming company is a business that develops, publishes, and/or operates digital games delivered over the internet, providing interactive entertainment and related services to players worldwide.
-
E.
streaming platform
A streaming platform is a digital service that delivers on-demand or live audio, video, or interactive content over the internet to users on connected 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_69e0b4a3320881909495ae8bc30bc2dc |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:24 a.m.