Triple
T37503595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Direct Neural Interface |
E932034
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fictional neural-augmentation technology |
C12903
|
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 neural-augmentation technology Context triple: [Direct Neural Interface, instanceOf, fictional neural-augmentation technology]
-
A.
fictional neural interface system
chosen
A fictional neural interface system is an imagined technology that directly links the human brain with computers or networks to enable seamless communication, control, and data exchange through thought alone.
-
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.
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.
-
D.
cybernetically augmented humanoids
Cybernetically augmented humanoids are beings whose biological bodies are enhanced or partially replaced with advanced technological systems to expand their physical, cognitive, or sensory capabilities beyond natural human limits.
-
E.
fictional robot
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.
- 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_69f76ec5268481909ea01c73aeeefd42 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:17 p.m.