Triple
T37303884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arx series |
E926027
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fantasy role-playing game franchise |
C10213
|
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: fantasy role-playing game franchise Context triple: [Arx series, instanceOf, fantasy role-playing game franchise]
-
A.
action role-playing game series
chosen
An action role-playing game series is a collection of related video games that blend real-time combat and character control with role-playing elements such as character progression, narrative choices, and equipment customization across multiple interconnected titles.
-
B.
epic fantasy novel series
An epic fantasy novel series is a multi-book narrative set in a richly imagined world, following expansive quests, complex characters, and large-scale conflicts often involving magic, mythology, and the fate of entire realms.
-
C.
role‑playing game
A role-playing game is an interactive experience in which players assume fictional characters and collaboratively create or influence a narrative by making choices that affect the game world and its outcomes.
-
D.
fantasy hero
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.
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.
- 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_69f76eb1bc508190924e9fa5d8acdeb3 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:16 p.m.