Triple
T8511116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lucky Starr series |
E201453
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | science fiction novel series |
C15165
|
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: science fiction novel series Context triple: [Lucky Starr series, instanceOf, science fiction novel series]
-
A.
science fiction novel
A science fiction novel is a long-form narrative that explores speculative futures, advanced technologies, or alternative realities to examine their impact on individuals, societies, and the nature of existence.
-
B.
fictional book series
chosen
A fictional book series is a collection of related narrative works set in the same imagined world, featuring recurring characters, settings, or overarching storylines that develop across multiple volumes.
-
C.
young adult science fiction series
A young adult science fiction series is a multi-book narrative set in speculative or futuristic worlds that follows teenage protagonists as they confront advanced technologies, societal upheavals, or extraterrestrial forces while navigating coming-of-age challenges.
-
D.
epic fantasy novel series
An epic fantasy novel series is a multi-book narrative set in a richly imagined world, following expansive quests, complex characters, and large-scale conflicts often involving magic, mythology, and the fate of entire realms.
-
E.
literary series
A literary series is a sequence of related written works, typically sharing common characters, settings, or overarching plotlines, published as multiple installments.
- 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_69ca8320e5748190ac2c585a0bba8193 |
completed | March 30, 2026, 2:05 p.m. |
Created at: March 30, 2026, 6:15 p.m.