Triple
T18206724
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bokanovsky Process |
E435920
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fictional reproductive technology |
C14843
|
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 reproductive technology Context triple: [Bokanovsky Process, instanceOf, fictional reproductive technology]
-
A.
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.
-
B.
fictional scientific project
A fictional scientific project is an imagined research endeavor, often set in a speculative or alternate reality, that explores hypothetical technologies, discoveries, or experiments to drive narrative, illustrate concepts, or examine ethical and societal implications of science.
-
C.
fictional phenomenon
chosen
A fictional phenomenon is an imagined event, process, or occurrence that exists only within the context of a narrative or invented world, governed by that setting’s own internal logic rather than real-world science.
-
D.
fictional artifact
A fictional artifact is an imagined object within a narrative world that possesses specific properties, functions, or symbolic meaning but does not exist in reality.
-
E.
fictional pathogen
A fictional pathogen is an imagined biological agent—such as a virus, bacterium, or parasite—created within a narrative or speculative context to cause disease, drive plot events, or explore scientific and ethical themes.
- 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_69d8b90dba6481908e119eb9aa4ca0cb |
completed | April 10, 2026, 8:47 a.m. |
Created at: April 10, 2026, 10:32 a.m.