Triple
T15385880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Crait |
E367914
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | event in Star Wars canon |
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 canon Context triple: [Battle of Crait, instanceOf, event in Star Wars canon]
-
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.
region in the Star Wars galaxy
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.
-
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.
Star Wars anthology film
A Star Wars anthology film is a standalone movie set within the Star Wars universe that explores side stories, characters, or events outside the main episodic saga.
- 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_69d85a1551a08190ba2caea7cd51c639 |
completed | April 10, 2026, 2:01 a.m. |
Created at: April 10, 2026, 3:19 a.m.