Triple
T20793248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dragon Age series |
E511832
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | role-playing video 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: role-playing video game franchise Context triple: [Dragon Age series, instanceOf, role-playing video 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.
platform game series
A platform game series is a collection of related video games, typically sharing characters, settings, and core mechanics, in which players navigate environments by running, jumping, and overcoming obstacles across multiple installments.
-
C.
stealth video game franchise
A stealth video game franchise is a series of games centered on avoiding detection through careful movement, strategy, and use of the environment to complete objectives covertly.
-
D.
video game brand
A video game brand is a recognizable identity encompassing a series of games, characters, visual styles, and values that collectively distinguish and market a company's gaming products to consumers.
-
E.
handheld electronic game series
A handheld electronic game series is a collection of related portable, self-contained electronic games sharing common branding, themes, or gameplay elements, typically designed for play on dedicated handheld devices.
- 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_69e0b4cb83948190bd57bec21d78ed53 |
completed | April 16, 2026, 10:07 a.m. |
Created at: April 16, 2026, 12:38 p.m.