Triple
T15575986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yandex |
E374370
|
entity |
| Predicate | hasService |
P182
|
FINISHED |
| Object | Yandex Music |
E1099164
|
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: Yandex Music | Statement: [Yandex, hasService, Yandex Music]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yandex Music Context triple: [Yandex, hasService, Yandex Music]
-
A.
Yandex Music
chosen
Yandex Music is a Russian music streaming service and recommendation platform operated by the technology company Yandex.
-
B.
VK Music
VK Music is a Russian music streaming and audio platform integrated into the VK social network, offering on-demand listening, playlists, and recommendations.
-
C.
Yandex Zen
Yandex Zen is a personalized content recommendation and news feed platform that delivers articles, videos, and other media based on users’ interests and browsing behavior.
-
D.
Deezer
Deezer is a global music streaming service offering on-demand access to a large catalog of songs, playlists, and podcasts across multiple platforms.
-
E.
Spotify
Spotify is a popular digital music, podcast, and video streaming service that offers on-demand and curated audio content across multiple platforms.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d85ccd575081908909b71a3f3e3a61 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e2140388190a8df7b835eaa72ce |
completed | April 16, 2026, 2:49 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff4c4978ec8190a57de5d9a2ec6653 |
completed | May 9, 2026, 3:01 p.m. |
Created at: April 10, 2026, 4:10 a.m.