Triple
T32066719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kairi |
E818900
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Kingdom Hearts character |
C60196
|
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: Kingdom Hearts character Context triple: [Kairi, instanceOf, Kingdom Hearts 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.
Fate series character
A Fate series character is a heroic or mythical figure summoned as a powerful "Servant" with unique abilities, Noble Phantasms, and a distinct personality shaped by both legend and the narrative’s reinterpretation.
-
C.
Fate/Grand Order character
A Fate/Grand Order character is a summoned heroic spirit or mythic figure, reimagined with unique abilities, personality, and narrative role within the game's overarching story and combat system.
-
D.
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.
-
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. 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_69f348fecc088190af1470afe5a969f0 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:22 a.m.