Triple
T14422806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yandex Translate |
E357623
|
entity |
| Predicate | supportsLanguagePairDirection |
P20095
|
FINISHED |
| Object | Russian–English |
—
|
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: Russian–English | Statement: [Yandex Translate, supportsLanguagePairDirection, Russian–English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsLanguagePairDirection Context triple: [Yandex Translate, supportsLanguagePairDirection, Russian–English]
-
A.
languagePair
Indicates a relationship that associates two specific languages as a paired combination, typically for translation, comparison, or mapping between them.
-
B.
canTranslateBetween
Indicates that an entity has the ability to translate or convert information accurately between two specified languages, formats, or representation systems.
-
C.
translationDirection
chosen
Indicates the source and target languages involved in a translation, specifying the direction from the original language to the translated language.
-
D.
coexistsWithLanguage
Indicates that one entity exists or functions alongside a particular language at the same time, without excluding or replacing it.
-
E.
supportsLanguageOverrides
Indicates that an entity allows its default behavior or settings to be modified based on specific language selections or preferences.
- 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.