Triple
T25201689
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Game Awards |
E631139
|
entity |
| Predicate | hasPart |
P35
|
FINISHED |
| Object |
Players' Voice award
The Players' Voice award is a fan-voted honor at The Game Awards that recognizes the year's most popular game as chosen directly by players.
|
E1666639
|
NE 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: Players' Voice award | Statement: [The Game Awards, hasPart, Players' Voice award]
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Players' Voice award Triple: [The Game Awards, hasPart, Players' Voice award]
Generated description
The Players' Voice award is a fan-voted honor at The Game Awards that recognizes the year's most popular game as chosen directly by players.
Provenance (5 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_69e75a8b86c4819089eda22c843b739f |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f474b904f48190be6513788f89c6a9 |
completed | May 1, 2026, 9:39 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a105d2e828481908a413f5da300e861 |
completed | May 22, 2026, 1:42 p.m. |
| NEDg | Description generation | batch_6a105e53f9bc8190a4b0929a68d83b0a |
completed | May 22, 2026, 1:47 p.m. |
| NED2 | Entity disambiguation (via description) | batch_6a105edf54888190a3b77f63eb867749 |
completed | May 22, 2026, 1:49 p.m. |
Created at: April 21, 2026, 12:51 p.m.