Triple
T29188238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Galactic Alliance |
E739927
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Star Wars Legends organization |
C23323
|
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 Legends organization Context triple: [Galactic Alliance, instanceOf, Star Wars Legends organization]
-
A.
Star Wars organization
chosen
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.
-
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.
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 family
A Star Wars family is a group of characters connected by blood, adoption, or close emotional bonds whose relationships significantly influence the saga’s central conflicts, legacies, and themes of destiny and redemption.
-
E.
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.
- 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_69f07cb8033c8190b8807e219a14333d |
completed | April 28, 2026, 9:24 a.m. |
Created at: April 28, 2026, 12:01 p.m.