Triple
T30228933
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mandalorian Wars |
E768570
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | event in Star Wars Legends continuity |
C32743
|
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: event in Star Wars Legends continuity Context triple: [Mandalorian Wars, instanceOf, event in Star Wars Legends continuity]
-
A.
event in the Star Wars universe
chosen
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.
-
B.
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."
-
C.
game in the Star Wars universe
A game in the Star Wars universe is an interactive experience that immerses players in the franchise’s iconic settings, characters, and conflicts, allowing them to participate in stories and actions consistent with Star Wars lore.
-
D.
Star Wars Legends character
A Star Wars Legends character is a fictional individual from the non-canonical expanded universe of Star Wars media, including books, comics, games, and other stories outside the official film-based continuity.
-
E.
Star Wars franchise element
A Star Wars franchise element is any distinct character, location, object, species, event, or concept that exists within the narrative universe of the Star Wars media franchise.
- 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_69f2248108208190be60bf1af343ce70 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:36 p.m.