Triple
T20191509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marth |
E492988
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Fire Emblem character |
C4830
|
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: Fire Emblem character Context triple: [Marth, instanceOf, Fire Emblem character]
-
A.
The King of Fighters character
A King of Fighters character is a distinct, stylized combatant with unique fighting techniques, personality, and backstory, designed to participate in the series’ team-based martial arts tournaments.
-
B.
Nibelungen saga character
A Nibelungen saga character is a mythic figure from the medieval Germanic epic cycle, often entangled in themes of heroism, betrayal, and tragic fate within the world of dragons, cursed treasure, and royal feuds.
-
C.
video game character
chosen
A video game character is a fictional, interactive entity within a game world that the player controls or encounters, defined by its abilities, appearance, behavior, and role in the game's narrative or mechanics.
-
D.
anime character
An anime character is a stylized, often exaggerated fictional persona originating from Japanese animation, defined by distinctive visual design, expressive emotions, and participation in narrative-driven stories.
-
E.
character from Warcraft franchise
A character from the Warcraft franchise is a fictional individual—such as a hero, villain, or supporting figure—who exists within the Warcraft universe’s lore, games, and media, possessing distinct abilities, backstory, and affiliations with its various races and factions.
- 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_69da6268a034819081cbd9ea5a1c9475 |
completed | April 11, 2026, 3:02 p.m. |
Created at: April 11, 2026, 11:37 p.m.