Triple
T15311431
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hyper Light Drifter (video game soundtrack) |
E366046
|
entity |
| Predicate | platformReleasedOn |
P44893
|
FINISHED |
| Object | digital distribution |
—
|
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: digital distribution | Statement: [Hyper Light Drifter (video game soundtrack), platformReleasedOn, digital distribution]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: platformReleasedOn Context triple: [Hyper Light Drifter (video game soundtrack), platformReleasedOn, digital distribution]
-
A.
pcReleaseDate
Indicates the calendar date on which something becomes publicly available or is launched specifically for personal computers.
-
B.
yearAnnounced
Indicates the calendar year in which something (such as a product, event, or decision) was formally announced.
-
C.
consoleReleaseDate
Indicates the calendar date on which a particular game console was first released to the public.
-
D.
releaseDateOnPlatform
chosen
Indicates the date on which a particular item (e.g., a product, game, or media) becomes available on a specific platform.
-
E.
videoGameReleaseYear
Indicates the calendar year in which a particular video game was released.
- 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_69d85a113ee881908e297a1d38dd79fa |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03cd2d5a88190aead748920f93d47 |
completed | April 16, 2026, 1:35 a.m. |
| PD | Predicate disambiguation | batch_69deca935e2c8190b640987ddfc542b9 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:16 a.m.