Triple
T23740884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plan B (Interstellar) |
E586667
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fictional contingency plan |
C24516
|
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 contingency plan Context triple: [Plan B (Interstellar), instanceOf, fictional contingency plan]
-
A.
fictional plan
chosen
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.
fictionalEvent
A fictionalEvent represents an invented occurrence or happening within a narrative world, defined by its time, place, participants, and narrative significance.
-
C.
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.
-
D.
fictional setting
A fictional setting is an imagined world or environment, with its own locations, cultures, and rules, in which the events of a story take place.
-
E.
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.
- 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_69e24908efb08190bf755c3a9b91f222 |
completed | April 17, 2026, 2:51 p.m. |
Created at: April 17, 2026, 7:11 p.m.