Triple
T20333437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paradice project |
E492542
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fictional genetic engineering project |
C27000
|
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 genetic engineering project Context triple: [Paradice project, instanceOf, fictional genetic engineering project]
-
A.
fictional scientific project
chosen
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.
-
B.
genetically engineered superhuman
A genetically engineered superhuman is an individual whose DNA has been deliberately modified to enhance physical, mental, or other abilities far beyond typical human limits.
-
C.
fictional military program
A fictional military program is an imagined, often secretive initiative or project within an armed forces setting, designed to explore advanced technologies, strategies, or operations that drive the narrative in speculative or military-themed stories.
-
D.
fictional power plant
A fictional power plant is an imagined facility that generates and distributes energy within a narrative world, often using speculative technologies or fantastical resources to power societies, devices, or plot events.
-
E.
fictional plan
A fictional plan is an imagined, often detailed strategy or course of action that exists only within a narrative, scenario, or conceptual context rather than in real-world implementation.
- 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_69e0b4a1a09881908d97270d6971a25a |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:22 a.m.