Triple
T36828126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AI (The Answer) |
E910064
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | artificial intelligence in fiction |
C13208
|
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: artificial intelligence in fiction Context triple: [AI (The Answer), instanceOf, artificial intelligence in fiction]
-
A.
cultural concept of artificial intelligence
The cultural concept of artificial intelligence encompasses the shared beliefs, narratives, symbols, and expectations through which societies imagine, interpret, and emotionally respond to thinking machines and automated decision-making.
-
B.
artificial intelligence
Artificial intelligence is a field of computer science focused on creating systems that can perform tasks that typically require human intelligence, such as learning, reasoning, perception, and decision-making.
-
C.
scienceFictionWork
A scienceFictionWork is a creative narrative or artistic piece that explores speculative concepts based on imagined scientific, technological, or futuristic developments and their impact on individuals or societies.
-
D.
fictional computer
chosen
A fictional computer is an imagined computing device, often with advanced or impossible capabilities, that exists only within stories, games, or speculative scenarios.
-
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_69f76e7e9d60819092442fba73290a46 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:13 p.m.