Triple
T17509408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dragon Age: Inquisition (score) |
E426409
|
entity |
| Predicate | associatedGenreOfGame |
P38924
|
FINISHED |
| Object | fantasy role-playing game |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: fantasy role-playing game | Statement: [Dragon Age: Inquisition (score), associatedGenreOfGame, fantasy role-playing game]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedGenreOfGame Context triple: [Dragon Age: Inquisition (score), associatedGenreOfGame, fantasy role-playing game]
-
A.
gameGenreContext
Indicates the genre or type of game associated with a given game entity or gaming context.
-
B.
associatedWithGenreDevelopment
Indicates a relationship where something has contributed to, influenced, or been involved in the development or evolution of a particular genre.
-
C.
genreAssociatedWith
chosen
Indicates a relationship where a work, item, or entity is linked to or categorized under a particular genre.
-
D.
targetGenre
Indicates the genre that something is specifically aimed at, categorized under, or intended to belong to.
-
E.
websiteGenre
Indicates the thematic category or type of content that a website is primarily associated with.
- F. None of above.
Provenance (3 batches)
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_69d889dd9164819087b1dc3c9240c870 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4525a43208190b8728214767428c0 |
completed | April 19, 2026, 3:56 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f5fbcc8190a6ea9639bf5650da |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:48 a.m.