Triple
T38368450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beskar |
E892515
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | material in the Star Wars universe |
C54853
|
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: material in the Star Wars universe Context triple: [Beskar, instanceOf, material in the Star Wars universe]
-
A.
era in the Star Wars universe
An era in the Star Wars universe is a distinct span of in-universe time characterized by specific galactic events, political powers, and cultural conditions that define the setting for stories and conflicts.
-
B.
weapon in the Star Wars universe
A weapon in the Star Wars universe is any tool or device—ranging from primitive melee arms to advanced energy-based and superweapons—designed to inflict damage, exert control, or provide defense within the galaxy’s technological and mystical context.
-
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 franchise element
chosen
A Star Wars franchise element is any distinct character, location, object, species, event, or concept that exists within the narrative universe of the Star Wars media franchise.
- 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_69f76e47cb4c8190bdd92cd1db59c0c5 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:31 p.m.