Triple
T11563697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | D.I.C.E. Awards 2017 Game of the Year |
E274201
|
entity |
| Predicate | honorsWorksReleasedIn |
P30914
|
FINISHED |
| Object | 2016 |
—
|
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: 2016 | Statement: [D.I.C.E. Awards 2017 Game of the Year, honorsWorksReleasedIn, 2016]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: honorsWorksReleasedIn Context triple: [D.I.C.E. Awards 2017 Game of the Year, honorsWorksReleasedIn, 2016]
-
A.
eraOfWorkRelease
Indicates the historical or cultural era during which a work was originally released.
-
B.
notableWorkPublicationDate
Indicates the date on which a notable work associated with an entity was first published.
-
C.
notableWorkYear
Indicates the year in which a notable work associated with an entity was created, released, or achieved prominence.
-
D.
notableEditionYear
Indicates the year in which a particular edition of something (such as a work, product, or publication) is considered notable or significant.
-
E.
workReleaseYear
chosen
Indicates the calendar year in which a work (such as a book, film, or album) was first released or made publicly available.
- 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_69d6aae5ac3c81908d2b0a3a665665b2 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d88dd2016481909b33848af3d1d6c1 |
completed | April 10, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69d85dc3fc2c8190bed7e2111301a77c |
completed | April 10, 2026, 2:17 a.m. |
Created at: April 8, 2026, 9:37 p.m.