Triple
T29322100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hutt Cartel |
E743541
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Star Wars fictional 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 fictional organization Context triple: [Hutt Cartel, instanceOf, Star Wars fictional 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.
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.
-
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.
concept in the Star Wars universe
A concept in the Star Wars universe is an abstract idea, principle, or phenomenon—such as the Force, the Jedi Code, or hyperspace—that shapes the lore, culture, and conflicts of the galaxy far, far away.
-
E.
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.
- 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_69f09125f784819080f4e9fce9fe624f |
completed | April 28, 2026, 10:51 a.m. |
Created at: April 28, 2026, 1:24 p.m.