Triple
T9501932
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yuriĭ |
E229162
|
entity |
| Predicate | sharesEtymologyWith |
P28322
|
FINISHED |
| Object | Yuriy |
E229162
|
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: Yuriy | Statement: [Yuriĭ, sharesEtymologyWith, Yuriy]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yuriy Context triple: [Yuriĭ, sharesEtymologyWith, Yuriy]
-
A.
Yuriĭ
chosen
Yuriĭ is a given name of Slavic origin, commonly used as a variant of the name Yuri.
-
B.
Юрий
Юрий is a common Russian male given name, often rendered in English as Yuri and borne by numerous notable figures in Russian and Soviet history and culture.
-
C.
Yuri Filipchenko
Yuri Filipchenko was a Russian geneticist and entomologist who helped establish genetics as a scientific discipline in Russia and influenced early evolutionary biology.
-
D.
Anatoly
Anatoly is a masculine given name of Slavic origin, commonly used in Russian-speaking countries.
-
E.
Vitaly
Vitaly is a masculine given name of Slavic origin, commonly used in Russian-speaking countries.
- 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_69ca84753660819098e8d416e89e26ae |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd983d4b708190a4dfef1246986a26 |
completed | April 1, 2026, 10:12 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d2e4fa938881908253aed52870210d |
completed | April 5, 2026, 10:40 p.m. |
Created at: March 30, 2026, 7:57 p.m.