Triple
T29548556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Notron |
E749695
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Star Wars Legends location |
C32742
|
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 location Context triple: [Notron, instanceOf, Star Wars Legends location]
-
A.
Star Wars–themed location
A Star Wars–themed location is a setting inspired by the Star Wars universe, featuring iconic planets, architecture, characters, and technologies that immerse visitors or participants in its distinctive sci-fi atmosphere.
-
B.
region in the Star Wars galaxy
chosen
A region in the Star Wars galaxy is a large-scale spatial division of known space, encompassing multiple star systems, sectors, and hyperspace routes that share common political, cultural, or navigational characteristics.
-
C.
Star Trek location
A Star Trek location is any distinct place within the Star Trek universe—such as planets, starships, space stations, or regions of space—where narrative events, exploration, and interactions occur.
-
D.
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."
-
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.
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_69f0bd48691081908cecad39bac591e0 |
completed | April 28, 2026, 1:59 p.m. |
Created at: April 28, 2026, 5:10 p.m.