Triple
T21310513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yury of Moscow |
E525320
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Yury |
—
|
NE NERFINISHED |
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: Yury | Statement: [Yury of Moscow, givenName, Yury]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yury Context triple: [Yury of Moscow, givenName, Yury]
-
A.
Yuri
Yuri is a common Russian given name, famously borne by Yuri Gagarin, the first human to journey into outer space.
-
B.
Yuri
Yuri is a Papuan language belonging to the Karkar-Yuri language family of New Guinea.
-
C.
Юрий
chosen
Юрий 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.
-
D.
Yuri of Moscow
Yuri of Moscow was a 14th-century Grand Prince of Moscow and Vladimir who played a key role in the early rise of Muscovy through his political maneuvers and conflicts over the Vladimir-Suzdal throne.
-
E.
Leonid
Leonid is a masculine given name of Slavic origin, notably borne by Soviet leader Leonid Brezhnev.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b518b8948190ad69cf9a8784d397 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e75aab14f08190949e1407eb2b3e67 |
completed | April 21, 2026, 11:08 a.m. |
Created at: April 16, 2026, 4:09 p.m.