Triple
T37150613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Simon (Dungeons & Dragons: Honor Among Thieves) |
E920350
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Dungeons & Dragons character |
C49799
|
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: Dungeons & Dragons character Context triple: [Simon (Dungeons & Dragons: Honor Among Thieves), instanceOf, Dungeons & Dragons character]
-
A.
Dungeons & Dragons monster
A Dungeons & Dragons monster is a fantastical creature, entity, or adversary defined by game statistics, abilities, and lore, used by the Dungeon Master to challenge and enrich players’ adventures.
-
B.
Dungeons & Dragons licensed product
A Dungeons & Dragons licensed product is any officially authorized item—such as books, games, accessories, or digital content—that uses the D&D brand, settings, or rules under a formal license from its rights holder.
-
C.
Dungeons & Dragons location
A Dungeons & Dragons location is a distinct, narrative-rich setting—such as a town, dungeon, wilderness, or planar realm—designed to host adventures, encounters, and exploration within the game world.
-
D.
fantasy hero
chosen
A fantasy hero is a courageous protagonist, often possessing extraordinary abilities or destiny, who embarks on perilous quests in a magical or mythical world to confront evil and restore balance.
-
E.
board game character
A board game character is a distinct, often themed persona or token within a board game that represents a player’s role, abilities, and progression in the game’s world and mechanics.
- 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_69f76e9f87c08190b4c8f7fafbd8345a |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:15 p.m.