Triple
T37873020
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BlizzCon 2011 |
E944650
|
entity |
| Predicate | showcasedGame |
P169201
|
FINISHED |
| Object | Diablo III |
—
|
NE NERFINISHED |
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: Diablo III | Statement: [BlizzCon 2011, showcasedGame, Diablo III]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: showcasedGame Context triple: [BlizzCon 2011, showcasedGame, Diablo III]
-
A.
gameDemoed
chosen
Indicates that an instance of a game has been shown or demonstrated, typically in a preview or trial form, to an audience or user.
-
B.
videoGame
Indicates that one entity is a video game associated with, created by, or otherwise related to another entity.
-
C.
designedGame
Indicates that one entity is the creator or designer responsible for the conception and development of a particular game.
-
D.
notableGame
Indicates that a particular game is especially significant, prominent, or well-known in relation to the associated entity.
-
E.
relatedGame
Indicates that one game has a notable connection or association with another game, such as shared content, themes, or series.
- 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_69f76eef55d481908ca6660b4b532550 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbbae559a8819086ef839973f8d9b2 |
completed | May 6, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69fbb1440fa08190abf25ba684f75b6e |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:19 p.m.