Triple
T26630760
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alan Bradley |
E668483
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Tron character |
C51844
|
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: Tron character Context triple: [Alan Bradley, instanceOf, Tron character]
-
A.
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.
-
B.
Terminator character
A Terminator character is a relentless, human-like cyborg assassin from the future, typically sent back in time with a specific mission that often pits advanced machine intelligence against human survival.
-
C.
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.
-
D.
Speed Racer character
A Speed Racer character is a stylized, high-energy figure from the Speed Racer universe, defined by their role in high-stakes auto racing, distinctive retro-anime aesthetics, and dramatic, action-driven personality traits.
-
E.
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.
- 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_69ee9cff507c819092b95bf7219a702e |
completed | April 26, 2026, 11:17 p.m. |
Created at: April 27, 2026, 2:25 a.m.