Triple
T36191230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Android 15 |
E1046994
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Dragon Ball character |
C63645
|
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: Dragon Ball character Context triple: [Android 15, instanceOf, Dragon Ball character]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
Capcom character
A Capcom character is a fictional persona created by Capcom, typically appearing in one or more of the company’s video game franchises with distinct abilities, backstory, and visual design.
-
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. chosen
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_69f76e3d4fbc81908c159c7beeb4ce00 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:08 p.m.