Triple
T28177663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The T*Witches series |
E715940
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | young adult fantasy 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: young adult fantasy series Context triple: [The T*Witches series, instanceOf, young adult fantasy series]
-
A.
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.
-
B.
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.
-
C.
urban fantasy series
An urban fantasy series is a collection of interconnected stories set primarily in a contemporary, real-world city where magical, supernatural, or mythical elements secretly or openly coexist with everyday life.
-
D.
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.
-
E.
young adult book
A young adult book is a work of fiction or nonfiction written primarily for readers aged roughly 12–18, typically focusing on adolescent protagonists and themes of identity, growth, and personal challenges.
- 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_69efd6b4fc5c81909dd88f01a8c2b35d |
completed | April 27, 2026, 9:35 p.m. |
Created at: April 27, 2026, 10:17 p.m.