Triple
T14422876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yandex Zen |
E357624
|
entity |
| Predicate | usesForPersonalization |
P111922
|
FINISHED |
| Object | user reading history |
—
|
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: user reading history | Statement: [Yandex Zen, usesForPersonalization, user reading history]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesForPersonalization Context triple: [Yandex Zen, usesForPersonalization, user reading history]
-
A.
supportsPersonalization
chosen
Indicates that one entity enables or provides functionality for tailoring content, behavior, or experience to the preferences or characteristics of another entity.
-
B.
usedByPerson
Indicates that something (such as an object, tool, or resource) is utilized or employed by a person.
-
C.
usesProfile
Indicates that one entity employs, operates under, or is associated with a particular profile in performing its actions or functions.
-
D.
usedFor
Indicates that one entity serves a purpose, function, or role in accomplishing, enabling, or supporting another entity or activity.
-
E.
partOfUse
Indicates that something functions as a component or constituent within the use or application of something else.
- 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_69d82793421c8190861eb0e673b085de |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de91102c3c81908f571a1fff3bdd47 |
completed | April 14, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69de5c30467881908e770e3940295641 |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:18 a.m.