Triple
T9787736
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bullseye |
E237530
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | character in the Toy Story franchise |
C22574
|
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: character in the Toy Story franchise Context triple: [Bullseye, instanceOf, character in the Toy Story franchise]
-
A.
Toy Story character
chosen
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.
-
B.
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.
-
C.
Jurassic Park character
A Jurassic Park character is an individual—human or dinosaur—whose actions, traits, and relationships drive the narrative of survival, science, and chaos within the dinosaur-filled Jurassic Park universe.
-
D.
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.
-
E.
Pixar short film
A Pixar short film is a brief, self-contained animated story created by Pixar that showcases inventive storytelling, distinctive characters, and cutting-edge animation techniques, often preceding their feature-length movies.
- 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_69ca84da927881909bda80caecad6010 |
completed | March 30, 2026, 2:12 p.m. |
Created at: March 30, 2026, 8:27 p.m.