Triple
T5080103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fire Emblem |
E114491
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | tactical role-playing game series |
C4648
|
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: tactical role-playing game series Context triple: [Fire Emblem, instanceOf, tactical role-playing game series]
-
A.
action role-playing game series
An action role-playing game series is a collection of related video games that blend real-time combat and character control with role-playing elements such as character progression, narrative choices, and equipment customization across multiple interconnected titles.
-
B.
role‑playing game
chosen
A role-playing game is an interactive experience in which players assume fictional characters and collaboratively create or influence a narrative by making choices that affect the game world and its outcomes.
-
C.
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.
-
D.
narrative-driven game
A narrative-driven game is an interactive experience where storytelling, character development, and plot progression are the primary focus, guiding gameplay and player choices.
-
E.
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.
- 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_69bd443dbf908190a9401e9c2dc7bd7d |
completed | March 20, 2026, 12:57 p.m. |
Created at: March 20, 2026, 1:39 p.m.