Triple
T29444657
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PC Gamer Game of the Year (1994, various regional editions) |
E746814
|
entity |
| Predicate | appliesToGameReleaseYear |
P53695
|
FINISHED |
| Object | 1994 |
—
|
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: 1994 | Statement: [PC Gamer Game of the Year (1994, various regional editions), appliesToGameReleaseYear, 1994]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToGameReleaseYear Context triple: [PC Gamer Game of the Year (1994, various regional editions), appliesToGameReleaseYear, 1994]
-
A.
videoGameReleaseYear
chosen
Indicates the calendar year in which a particular video game was released.
-
B.
sourceGameReleasePeriod
Indicates the time period during which the source game was originally released.
-
C.
eligibleReleaseYear
Indicates the year in which something qualifies or is permitted to be released according to specified criteria or rules.
-
D.
stableReleaseYear
Indicates the calendar year in which a stable, non-beta version of something (such as software or a product) was officially released.
-
E.
originalGamesYear
Indicates the year in which the original version of the game was first released.
- 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_69f0a7a230488190b44a97fe3d16f731 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69fd592e48cc81909d754cc6c4bd99ae |
completed | May 8, 2026, 3:31 a.m. |
| PD | Predicate disambiguation | batch_69fd58b7f9b881909dc099b28d567784 |
completed | May 8, 2026, 3:30 a.m. |
Created at: April 28, 2026, 3:26 p.m.