Triple
T30428193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zenitsu Agatsuma |
E774090
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Demon Slayer character |
C17512
|
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: Demon Slayer character Context triple: [Zenitsu Agatsuma, instanceOf, Demon Slayer character]
-
A.
Samurai Shodown character
A Samurai Shodown character is a distinct, weapon-focused combatant with unique fighting styles, special moves, and cultural or historical influences, designed for one-on-one dueling in the Samurai Shodown fighting game series.
-
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.
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.
-
D.
anime character
chosen
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.
Majipoor character
A Majipoor character is an inhabitant of Robert Silverberg’s vast, multi-species planet Majipoor, shaped by its layered political hierarchies, pervasive dream-control, and the cultural tensions between human settlers and native species.
- 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_69f22491ba248190b9a4776ca8e42d02 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 8:06 p.m.