Triple
T29417016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Call of Duty: Warzone live operations |
E746052
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | live service operations |
C23409
|
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: live service operations Context triple: [Call of Duty: Warzone live operations, instanceOf, live service operations]
-
A.
multiplayer services platform
A multiplayer services platform is a backend system that provides the networking, matchmaking, session management, and real-time communication infrastructure needed to support online multiplayer experiences across games or applications.
-
B.
service hub
A service hub is a centralized platform or location that coordinates, manages, and delivers a variety of services to users or connected systems.
-
C.
online video game service
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.
-
D.
service
chosen
A service is an intangible, value-creating activity or set of activities performed by a provider to meet the needs or solve the problems of a recipient, often without resulting in ownership of a physical product.
-
E.
through service
A through service is a transportation offering in which a vehicle or passenger travels from origin to destination across one or more intermediate points without requiring a transfer or change of service.
- 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_69f0a79f6d5c8190a350baed0157e06f |
completed | April 28, 2026, 12:27 p.m. |
Created at: April 28, 2026, 3:02 p.m.