Triple
T29100867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Total War |
E736636
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | strategy video game franchise |
C34192
|
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: strategy video game franchise Context triple: [Total War, instanceOf, strategy video game franchise]
-
A.
turn-based strategy game series
chosen
A turn-based strategy game series is a collection of related games in which players take discrete, alternating turns to make tactical and strategic decisions, often managing resources, units, and territories over multiple scenarios or campaigns.
-
B.
action video game series
An action video game series is a collection of related games that emphasize fast-paced combat, reflex-based challenges, and real-time gameplay across multiple installments sharing common themes, characters, or settings.
-
C.
stealth video game franchise
A stealth video game franchise is a series of games centered on avoiding detection through careful movement, strategy, and use of the environment to complete objectives covertly.
-
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.
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.
- 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_69f077ec765c81909474c88bcc8bab43 |
completed | April 28, 2026, 9:03 a.m. |
Created at: April 28, 2026, 11:12 a.m.