Triple
T18855808
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aftermath trilogy |
E461167
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | canon Star Wars work |
C41392
|
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: canon Star Wars work Context triple: [Aftermath trilogy, instanceOf, canon Star Wars work]
-
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.
Star Wars comic
A Star Wars comic is a graphic narrative set in the Star Wars universe that uses sequential art and dialogue to depict stories involving its characters, locations, and lore.
-
C.
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.
-
D.
Star Wars organization
A Star Wars organization is a structured group or faction within the Star Wars universe, defined by a common purpose, ideology, or function that influences galactic events and character relationships.
-
E.
event in the Star Wars universe
An event in the Star Wars universe is a significant occurrence or incident—such as a battle, political decision, personal confrontation, or galactic-scale crisis—that alters the state of characters, factions, or the broader timeline within the Star Wars narrative.
- 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_69d8dcfb7b9c8190854e7b171b98ea2e |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 10, 2026, 11:57 a.m.