Triple
T37456028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Steam Loyalist Upgrade |
E930801
|
entity |
| Predicate | genreOfBaseGame |
P53697
|
FINISHED |
| Object | action 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: action role-playing game | Statement: [Steam Loyalist Upgrade, genreOfBaseGame, action role-playing game]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: genreOfBaseGame Context triple: [Steam Loyalist Upgrade, genreOfBaseGame, action role-playing game]
-
A.
gameGenreContext
chosen
Indicates the genre or type of game associated with a given game entity or gaming context.
-
B.
gameGenreDeveloped
Indicates that a particular game genre has been created, defined, or developed by a specific entity (such as a person, team, or organization).
-
C.
primaryGameType
Indicates the main category or type of game with which an entity is primarily associated.
-
D.
videoGame
Indicates that one entity is a video game associated with, created by, or otherwise related to another entity.
-
E.
notableGameType
Indicates that a game is of a particular type or category for which the subject is especially well known or notable.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbacaf54648190811ea33b34907e8e |
completed | May 6, 2026, 9:03 p.m. |
| PD | Predicate disambiguation | batch_69fba883f770819091059c6f6c6af9f7 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:17 p.m.