Triple
T27810982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ronto Roasters |
E702517
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Star Wars–themed eatery |
C23321
|
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 eatery Context triple: [Ronto Roasters, instanceOf, Star Wars–themed eatery]
-
A.
Star Wars–themed location
chosen
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.
superhero-themed restaurant
A superhero-themed restaurant is a dining establishment that immerses guests in a comic-book universe through character-inspired decor, menu items, and interactive experiences.
-
C.
fictional-character-themed restaurant
A fictional-character-themed restaurant is a dining establishment whose decor, menu, staff presentation, and overall experience are designed around one or more specific fictional characters or franchises to create an immersive, story-driven atmosphere.
-
D.
aviation-themed restaurant
An aviation-themed restaurant is a dining establishment designed to evoke the experience of air travel or aviation history through decor, menu items, and ambiance inspired by airplanes, airports, and flight culture.
-
E.
Star Wars multimedia project
A Star Wars multimedia project is a coordinated collection of related Star Wars content—such as films, series, games, books, comics, and online media—designed to tell interconnected stories within the Star Wars universe across multiple platforms.
- 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_69ef840a16748190926719ab96120bae |
completed | April 27, 2026, 3:43 p.m. |
Created at: April 27, 2026, 5:42 p.m.