Triple
T14422895
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yandex ID |
E357625
|
entity |
| Predicate | appliesTo |
P1129
|
FINISHED |
| Object | Yandex Disk |
E357622
|
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 Disk | Statement: [Yandex ID, appliesTo, Yandex Disk]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yandex Disk Context triple: [Yandex ID, appliesTo, Yandex Disk]
-
A.
Yandex Disk
chosen
Yandex Disk is a cloud storage and file synchronization service by Yandex that lets users store, back up, and access files across devices.
-
B.
Naver Drive
Naver Drive is a cloud storage and file-sharing service provided by Naver, allowing users to store, sync, and access files across devices.
-
C.
VK Cloud
VK Cloud is a Russian cloud computing platform offering infrastructure and related services for businesses and developers, operated by the technology company VK.
-
D.
Dropbox
Dropbox is a cloud-based file storage and collaboration company known for enabling users to easily sync and share files across devices.
-
E.
Dropbox
Dropbox is an American hard rock band known for their melodic yet heavy sound and for their connections to the post-grunge and alternative metal scenes of the early 2000s.
- 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_69d82793421c8190861eb0e673b085de |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de91102c3c81908f571a1fff3bdd47 |
completed | April 14, 2026, 7:10 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd648784048190a9c7e95bfeec8b23 |
completed | May 8, 2026, 4:20 a.m. |
Created at: April 10, 2026, 1:18 a.m.