Triple
T33536579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Electronika 60 |
E858951
|
entity |
| Predicate | notableGameDeveloped |
P206506
|
FINISHED |
| Object | Tetris |
E244892
|
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: Tetris | Statement: [Electronika 60, notableGameDeveloped, Tetris]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableGameDeveloped Context triple: [Electronika 60, notableGameDeveloped, Tetris]
-
A.
notableGame
Indicates that a particular game is especially significant, prominent, or well-known in relation to the associated entity.
-
B.
notableConsoleGame
Indicates that a game is recognized as a significant or prominent title released for a particular video game console.
-
C.
notableGameEngineUse
Indicates that an entity is notably or prominently used as a game engine for another entity (such as a game or project).
-
D.
notableGameEngineFor
Indicates that a particular game engine is especially recognized or significant for developing or powering a given game or set of games.
-
E.
notableGameSupport
Indicates that an entity is recognized for providing significant support or contribution to a particular game.
- F. None of above. chosen
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_69f34978caf4819083f90eba4944d8e8 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a363c7b9cd88190a4a672ab3869eb6d |
completed | June 20, 2026, 7:08 a.m. |
| PD | Predicate disambiguation | batch_6a0379f505c88190ac0879ab422c3054 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7fb9f88190b384b1b68200aef0 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 1:39 a.m.