Triple
T15028096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mario & Luigi: Paper Jam |
E378268
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Mario & Luigi series game |
C20924
|
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: Mario & Luigi series game Context triple: [Mario & Luigi: Paper Jam, instanceOf, Mario & Luigi series game]
-
A.
Super Mario series video game
A Super Mario series video game is a platform-based interactive entertainment title featuring Mario and related characters navigating imaginative worlds, overcoming obstacles, and defeating enemies to achieve various goals.
-
B.
Mario franchise spin-off
chosen
A Mario franchise spin-off is a game or media work that features characters, settings, or elements from the main Super Mario series but focuses on different genres, gameplay styles, or narratives outside the core platforming adventures.
-
C.
Super Nintendo Entertainment System game
A Super Nintendo Entertainment System game is a video game designed to run on Nintendo's 16-bit SNES console, typically distributed on ROM cartridges and featuring the system’s characteristic graphics, sound, and controller-based gameplay.
-
D.
Famicom game
A Famicom game is a video game designed to run on Nintendo's Family Computer (Famicom) console, typically distributed on ROM cartridges and adhering to the system's hardware and technical limitations.
-
E.
Game Boy Advance game
A Game Boy Advance game is a software title specifically designed to run on Nintendo's Game Boy Advance handheld console, utilizing its hardware capabilities for portable interactive entertainment.
- 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_69d85cd46b2c819090d054c27787f677 |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 2:58 a.m.