Triple
T29417017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Call of Duty: Warzone live operations |
E746052
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | game live operations |
C55581
|
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: game live operations Context triple: [Call of Duty: Warzone live operations, instanceOf, game live operations]
-
A.
live dashboarding contest
A live dashboarding contest is a real-time competition where participants build, modify, and present interactive data dashboards under time constraints to solve analytical challenges and impress judges or an audience.
-
B.
remote gameplay feature
A remote gameplay feature enables players to access, control, and experience a game over a network from a different physical location than where the game is running.
-
C.
interactive sports league
An interactive sports league is a digitally enhanced competition platform where fans and participants can actively influence games, teams, and outcomes in real time through integrated media, data, and engagement tools.
-
D.
esports arena
An esports arena is a specialized venue designed and equipped to host competitive video gaming events, featuring professional-grade gaming setups, spectator seating, large display screens, and advanced audio-visual and networking infrastructure.
-
E.
sports management simulation mode
A sports management simulation mode is a gameplay feature where players act as team managers, making strategic decisions about rosters, finances, training, and tactics to guide a sports organization to success over time.
- F. None of above. chosen
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.