Triple
T16011316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ninjini |
E388342
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Skylander character |
C36842
|
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: Skylander character Context triple: [Ninjini, instanceOf, Skylander character]
-
A.
Transformers character
A Transformers character is a sentient robotic being from the Transformers universe, typically capable of transforming between a humanoid robot form and an alternate mode such as a vehicle, weapon, or creature, with distinct allegiance, personality, and abilities.
-
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.
Big Hero 6 character
A Big Hero 6 character is an individual—human, robot, or otherwise—who inhabits the futuristic city of San Fransokyo and contributes to the story’s blend of superhero action, emotional growth, and technological innovation.
-
D.
LEGO character
A LEGO character is a small, modular, and stylized figurine composed of interlocking plastic elements that represents a person, creature, or fictional entity within the LEGO system.
-
E.
Despicable Me character
A Despicable Me character is a whimsical, often exaggerated individual from the Despicable Me universe whose personality, appearance, and actions contribute to the franchise’s blend of comedy, heart, and mischief.
- 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_69d86dabcb7c8190b6a39d6831d2fa1b |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:55 a.m.