Triple
T9305383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vega signal project |
E223871
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fictional scientific 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 scientific project Context triple: [Vega signal project, instanceOf, fictional scientific project]
-
A.
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.
-
B.
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.
-
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.
fictional research institution
A fictional research institution is an imagined organization dedicated to conducting systematic investigation and experimentation, often serving as a setting or driver for scientific, technological, or societal developments within a narrative.
-
E.
fictional phenomenon
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.
- F. None of above. chosen
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_69ca8424d0f08190831e2e93c6533aeb |
completed | March 30, 2026, 2:09 p.m. |
Created at: March 30, 2026, 7:36 p.m.