Triple
T19217306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GameLine |
E480520
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | dial-up video game delivery service |
C38379
|
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: dial-up video game delivery service Context triple: [GameLine, instanceOf, dial-up video game delivery service]
-
A.
online video game service
chosen
An online video game service is a platform that delivers interactive games over the internet, enabling users to access, play, and often purchase or subscribe to games, while providing features such as matchmaking, social interaction, and digital content management.
-
B.
Nintendo network service
A Nintendo network service is an online platform provided by Nintendo that enables digital distribution, multiplayer connectivity, account management, and related online features for Nintendo gaming systems and software.
-
C.
cable television service
A cable television service is a subscription-based system that delivers a variety of television channels and related content to consumers via coaxial or fiber-optic cables.
-
D.
home video game hardware
Home video game hardware is a dedicated electronic device designed to run video games on a television or display, typically using game media or digital downloads and controlled via gamepads or other input devices.
-
E.
home video game console
A home video game console is a dedicated electronic device designed to connect to a television or display and run video games using physical or digital media, typically operated with handheld controllers in a domestic setting.
- 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_69d8e8cb8c348190b52075823911c869 |
completed | April 10, 2026, 12:10 p.m. |
Created at: April 10, 2026, 1:23 p.m.