Triple
T25286755
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Game Awards 2019 Game of the Year |
E633961
|
entity |
| Predicate | genreEligibility |
P125590
|
FINISHED |
| Object | any video game genre |
—
|
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: any video game genre | Statement: [The Game Awards 2019 Game of the Year, genreEligibility, any video game genre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: genreEligibility Context triple: [The Game Awards 2019 Game of the Year, genreEligibility, any video game genre]
-
A.
genreRestriction
Indicates that there is a limitation or constraint on which genres are allowed or applicable in a given context.
-
B.
hasGenreEligibility
chosen
Indicates that an entity qualifies to be categorized under a particular genre according to defined criteria.
-
C.
genreIncludes
Indicates that a broader genre category encompasses or contains a specified subgenre or work as part of its classification.
-
D.
supportedGenre
Indicates that an entity (such as a system, service, or tool) is capable of handling, providing, or working with a specified genre.
-
E.
hasTargetGenreCategory
Indicates that something is associated with or classified under a specific target genre category.
- 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_69e75a9402fc81909362ca85277c06d9 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f5ffc74fa481909b4fe24a9337f9eb |
completed | May 2, 2026, 1:44 p.m. |
| PD | Predicate disambiguation | batch_69f5f7f99dc08190afcfb3bc4dfbec1d |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 21, 2026, 1:19 p.m.