Triple
T15466120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Villager |
E372034
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Super Smash Bros. fighter |
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: Super Smash Bros. fighter Context triple: [Villager, instanceOf, Super Smash Bros. fighter]
-
A.
Nintendo character
A Nintendo character is a fictional persona created or licensed by Nintendo that appears in its video games, media, and related merchandise, often embodying distinctive abilities, personalities, and roles within their respective game worlds.
-
B.
MonsterVerse character
A MonsterVerse character is a fictional being—often a giant monster, titan, or associated human figure—originating from the shared cinematic universe that includes Godzilla, Kong, and related creatures, defined by its role within that interconnected storyline.
-
C.
Hammer Bro variant
A Hammer Bro variant is an enemy type that modifies the standard Hammer Bro’s behavior, appearance, or attack pattern—such as projectile type, movement style, or defensive traits—while retaining its core role as a mobile, hammer-throwing obstacle.
-
D.
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.
-
E.
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.
- 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_69d85cc8bd308190886949510b42e764 |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 3:33 a.m.