Triple
T33118413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dorian |
E847522
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Fictional android character |
C5782
|
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: Fictional android character Context triple: [Dorian, instanceOf, Fictional android character]
-
A.
fictional robot
chosen
A fictional robot is an imagined artificial being, typically mechanical or digital, designed with varying degrees of intelligence and autonomy to perform tasks, interact with characters, or explore themes about technology and humanity in stories.
-
B.
fictional cyborg
A fictional cyborg is a being that combines organic life with mechanical or electronic enhancements, often exploring themes of identity, humanity, and the boundary between man and machine.
-
C.
Blade Runner character
A Blade Runner character is an individual—human, replicant, or ambiguous—whose identity, morality, and purpose are explored within the dystopian, neo-noir world of the Blade Runner universe.
-
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.
fictional device
A fictional device is an imagined tool, machine, or piece of technology that does not exist in reality but is created within a narrative to serve specific plot, thematic, or world-building purposes.
- 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_69f3495751a081909850af5843da40dc |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:27 a.m.