Triple
T37663229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Axel |
E937761
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Minecraft: Story Mode 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: Minecraft: Story Mode character Context triple: [Axel, instanceOf, Minecraft: Story Mode character]
-
A.
Kingdom Hearts character
A Kingdom Hearts character is an individual—original or from various Disney, Square Enix, or other crossover worlds—who exists within the interconnected, magic-filled universe of Kingdom Hearts and participates in its battles between light and darkness.
-
B.
Pokémon character
A Pokémon character is a fictional creature with distinct species traits, abilities, and evolutionary potential that can be trained, battled, and formed emotional bonds with in the Pokémon universe.
-
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.
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.
-
E.
Steven Universe character
A Steven Universe character is an individual—human, Gem, or fusion—within the Steven Universe universe, defined by their unique gem-based abilities, personality, relationships, and role in the overarching narrative.
- 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:18 p.m.