Triple
T27810952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ronto Wrap |
E702516
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Star Wars–themed food |
C53386
|
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–themed food Context triple: [Ronto Wrap, instanceOf, Star Wars–themed food]
-
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.
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 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.
-
D.
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.
-
E.
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.
- F. None of above. chosen
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_69ef840a16748190926719ab96120bae |
completed | April 27, 2026, 3:43 p.m. |
Created at: April 27, 2026, 5:42 p.m.