Triple
T29188335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | C-canon (pre-2014 Lucasfilm canon hierarchy) |
E739929
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Star Wars canon level |
C54747
|
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: Star Wars canon level Context triple: [C-canon (pre-2014 Lucasfilm canon hierarchy), instanceOf, Star Wars canon level]
-
A.
Star Wars Legends work
A Star Wars Legends work is any story, book, comic, game, or other media set in the Star Wars universe that exists outside the official Disney-era canon, typically published before April 2014 or explicitly labeled as "Legends."
-
B.
canon Star Wars book
A canon Star Wars book is an officially recognized story within the primary Star Wars continuity that expands on the universe, characters, and events established by the films and other sanctioned media.
-
C.
Star Wars novel series
A Star Wars novel series is a collection of interconnected books set in the Star Wars universe that expand on its characters, events, and lore beyond the films.
-
D.
canon Star Wars work
A canon Star Wars work is any officially recognized story or reference material—such as films, TV series, novels, comics, or games—that Lucasfilm currently includes as part of the authoritative Star Wars continuity.
-
E.
Star Wars Legends concept
A Star Wars Legends concept is any character, event, technology, or idea originating from the non-canonical Expanded Universe materials—such as older novels, comics, and games—that exist outside the official Disney-era Star Wars continuity.
- 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_69f07cb8033c8190b8807e219a14333d |
completed | April 28, 2026, 9:24 a.m. |
Created at: April 28, 2026, 12:01 p.m.