Triple
T30774225
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Izaya Orihara |
E783612
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Manga 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: Manga character Context triple: [Izaya Orihara, instanceOf, Manga character]
-
A.
Nasuverse character
A Nasuverse character is an individual—human, supernatural, or conceptual—originating from Kinoko Nasu’s shared universe (e.g., Fate, Tsukihime, Kara no Kyoukai) whose identity, abilities, and role are defined by that setting’s intricate metaphysics, timelines, and lore.
-
B.
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.
-
C.
manga artist
A manga artist is a creator who conceptualizes, illustrates, and often writes sequential art stories in the distinctive style of Japanese comics, combining visual storytelling, character design, and panel composition to convey narrative and emotion.
-
D.
comic book character
A comic book character is a fictional persona, often possessing distinctive abilities, traits, or backstory, that appears in sequential art narratives and drives the plot through their actions and development.
-
E.
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.
- 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_69f224b1519081908b9db003fd2073e0 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:40 p.m.