Triple
T9045686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Юрий |
E216748
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Юры |
E218066
|
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: Юры | Statement: [Юрий, hasVariant, Юры]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Юры Context triple: [Юрий, hasVariant, Юры]
-
A.
Yuryatin
Yuryatin is a fictional Russian town in Boris Pasternak’s novel "Doctor Zhivago," serving as a key setting in Lara Antipova’s story.
-
B.
Vyatka
Vyatka was a historic region and town in northeastern European Russia, known as a frontier area that was gradually incorporated into the centralized Russian state.
-
C.
Yura
chosen
Yura is a common Slavic diminutive form of the male given name Yuri (or Yuriy), often used as a familiar or affectionate nickname.
-
D.
Khovrino
Khovrino is a Moscow Metro station serving as the northern terminus of the Zamoskvoretskaya Line.
-
E.
Vyazemsky
Vyazemsky is a small town in Russia’s Far Eastern Federal District, serving as an administrative center within Khabarovsk Krai.
- 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_69ca83d22d488190adbce5e020e9cd1d |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc6b148b188190814d64acae493634 |
completed | April 1, 2026, 12:47 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d047665204819090fe9c74fd64659e |
completed | April 3, 2026, 11:04 p.m. |
Created at: March 30, 2026, 7:09 p.m.