Triple
T8412870
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mortal Kombat |
E198664
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fighting game series |
C24295
|
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: fighting game series Context triple: [Mortal Kombat, instanceOf, fighting game series]
-
A.
crossover fighting game series
A crossover fighting game series is a collection of fighting games that brings together characters, settings, and mechanics from multiple distinct franchises into a unified, competitive gameplay experience.
-
B.
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.
-
C.
martial arts dynasty
A martial arts dynasty is a multigenerational lineage or ruling family whose identity, power, and legacy are built around the mastery, preservation, and transmission of a distinctive martial arts tradition.
-
D.
action-adventure game series
An action-adventure game series is a collection of related video games that blend real-time combat, exploration, and puzzle-solving within a continuous narrative universe or recurring thematic framework.
-
E.
basketball video game series
A basketball video game series is a recurring franchise of interactive digital games that simulate the sport of basketball, often featuring evolving gameplay mechanics, updated rosters, and improved graphics across multiple installments.
- 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_69ca831201b481909e137936ef99ff11 |
completed | March 30, 2026, 2:05 p.m. |
Created at: March 30, 2026, 6:06 p.m.