Triple
T36964638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STEM experiments in Beacon Mental Hospital |
E914394
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fictional scientific experiment |
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 scientific experiment Context triple: [STEM experiments in Beacon Mental Hospital, instanceOf, fictional scientific experiment]
-
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.
historical scientific experiment
A historical scientific experiment is a past, systematically conducted test or investigation designed to explore, demonstrate, or validate scientific principles, whose methods and outcomes have influenced the development of scientific knowledge over time.
-
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.
experimental journal
An experimental journal is a structured record where researchers systematically document the design, procedures, observations, data, and interpretations of experiments over time.
-
E.
alien experiment
A covert scientific procedure conducted by extraterrestrial beings on living subjects, often involving advanced technology and unknown objectives.
- 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_69f76e8c498c8190b2842db80aea8b3b |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:14 p.m.