Triple
T14422893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yandex ID |
E357625
|
entity |
| Predicate | appliesTo |
P1129
|
FINISHED |
| Object | Yandex Search |
E357620
|
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 Search | Statement: [Yandex ID, appliesTo, Yandex Search]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yandex Search Context triple: [Yandex ID, appliesTo, Yandex Search]
-
A.
Yandex Search
chosen
Yandex Search is a Russian-developed web search engine that powers Yandex’s ecosystem of online services and tools.
-
B.
Qwant
Qwant is a French privacy-focused search engine that emphasizes user anonymity and does not track or profile its users.
-
C.
Yandex
Yandex is a major Russian multinational technology company best known for its internet search engine and wide range of online services.
-
D.
Yahoo! Search
Yahoo! Search is a web search engine developed by Yahoo that was once one of the most popular gateways for finding information on the internet.
-
E.
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.
- 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_69fd5bcd2a908190ad7d5ebf11b41551 |
completed | May 8, 2026, 3:43 a.m. |
Created at: April 10, 2026, 1:18 a.m.