Triple
T20573738
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MultiVersus |
E505161
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | crossover fighting game |
C12897
|
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: crossover fighting game Context triple: [MultiVersus, instanceOf, crossover fighting game]
-
A.
crossover fighting game series
chosen
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.
fighting game series
A fighting game series is a collection of related video games centered on competitive combat between characters, typically featuring recurring fighters, mechanics, and story elements across multiple installments.
-
C.
crossover franchise
A crossover franchise is a media property that combines characters, settings, or storylines from two or more distinct fictional universes into a unified narrative or series.
-
D.
3D fighting game
A 3D fighting game is a video game where players control characters in three-dimensional arenas to engage in close-quarters combat using a combination of attacks, defenses, and special moves.
-
E.
boxing family
A boxing family is a group of closely related individuals connected by blood or marriage who are collectively involved in the sport of boxing, whether as fighters, trainers, promoters, or dedicated supporters.
- 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_69e0b4b721588190993ac7b0a9be2736 |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:39 a.m.