Triple
T1528785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Isaac |
E32393
|
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: [Isaac, 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.
fictionalCharacter
A fictionalCharacter is an invented person or being in a narrative work, defined by attributes, relationships, and actions that drive the story and embody its themes.
-
C.
animated character
An animated character is a fictional persona brought to life through drawn, computer-generated, or stop-motion imagery, exhibiting movement, expression, and personality within animated media.
-
D.
video game fictional entity
A video game fictional entity is any imagined character, creature, object, or construct that exists within the narrative or interactive world of a video game, defined by its designed attributes, behaviors, and role in gameplay or story.
-
E.
fictional persona
A fictional persona is an invented character with distinct traits, background, and motivations, created to embody perspectives or roles within a narrative or conceptual context.
- 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_69a885e9b0ac819093a9806ad0efc82c |
completed | March 4, 2026, 7:20 p.m. |
Created at: March 4, 2026, 7:26 p.m.