Triple
T38147916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Call of Duty: Modern Warfare |
E952669
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | video game subseries |
C65606
|
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: video game subseries Context triple: [Call of Duty: Modern Warfare, instanceOf, video game subseries]
-
A.
platform game series
A platform game series is a collection of related video games, typically sharing characters, settings, and core mechanics, in which players navigate environments by running, jumping, and overcoming obstacles across multiple installments.
-
B.
virtual reality game series
A virtual reality game series is a collection of interconnected VR games that share common settings, characters, or storylines, designed to provide immersive, interactive experiences across multiple installments.
-
C.
puzzle video game series
A puzzle video game series is a collection of related games that challenge players to solve logic, pattern, or spatial problems through progressively complex and often thematically connected gameplay.
-
D.
science fiction video game series
A science fiction video game series is a collection of related games set in futuristic or speculative worlds that explore advanced technology, space travel, alien life, or other science-based imaginative concepts through interactive storytelling and gameplay.
-
E.
video game edition
A video game edition is a specific packaged version of a video game that may include distinct content, features, bonuses, or physical/digital extras compared to the standard release.
- 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_69f76f0a67f4819080c492f61d688fcc |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:21 p.m.