Triple
T13197111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Princess Unikitty |
E314140
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | LEGO character |
C32617
|
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: LEGO character Context triple: [Princess Unikitty, instanceOf, LEGO character]
-
A.
G.I. Joe character
A G.I. Joe character is a fictional military-themed action hero or villain, each with a distinct code name, specialty, personality, and backstory within the G.I. Joe universe.
-
B.
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.
-
C.
Nintendo character
A Nintendo character is a fictional persona created or licensed by Nintendo that appears in its video games, media, and related merchandise, often embodying distinctive abilities, personalities, and roles within their respective game worlds.
-
D.
character in the Robot series
A character in the Robot series is an individual—human, robot, or other sentient entity—whose actions, decisions, and interactions drive the exploration of robotics, ethics, and society within Asimov’s interconnected universe.
-
E.
Toy Story character
A Toy Story character is a sentient toy from the Toy Story universe whose personality, relationships, and adventures explore themes of friendship, loyalty, and identity in a world where toys come to life when humans aren’t watching.
- 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_69d806ae1e08819090d95bfe1538cc17 |
completed | April 9, 2026, 8:06 p.m. |
Created at: April 9, 2026, 9:16 p.m.