Triple
T15575980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yandex |
E374370
|
entity |
| Predicate | hasService |
P182
|
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, hasService, Yandex Search]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yandex Search Context triple: [Yandex, hasService, 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.
OpenSearch
OpenSearch is an open-source, community-driven search and analytics engine and suite derived from Elasticsearch, used for full-text search, log analytics, and observability at scale.
-
E.
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.
- 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.