Triple
T16379401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Witcher |
E397759
|
entity |
| Predicate | notableGameAward |
P86816
|
FINISHED |
| Object | Game of the Year awards for The Witcher 3: Wild Hunt |
—
|
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: Game of the Year awards for The Witcher 3: Wild Hunt | Statement: [The Witcher, notableGameAward, Game of the Year awards for The Witcher 3: Wild Hunt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableGameAward Context triple: [The Witcher, notableGameAward, Game of the Year awards for The Witcher 3: Wild Hunt]
-
A.
notableGame
Indicates that a particular game is especially significant, prominent, or well-known in relation to the associated entity.
-
B.
isGameSpecificAward
chosen
Indicates that an award is specific to a particular game rather than being general or cross-game.
-
C.
notableAwardWon
Indicates that an entity has received a specific notable award as a winner.
-
D.
notableAwardedFor
Indicates that an award is notable specifically for being given in recognition of a particular work, achievement, or contribution.
-
E.
notableAwardRecognition
Indicates that an entity has received or been formally recognized with a notable award or honor.
- 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_69d87f2880b48190ae1a9673a3bbef80 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e319da3c6c8190a9ccf744996c31e8 |
completed | April 18, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69e226f94dd48190b7b8e0e983738a67 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:08 a.m.