Triple
T23438617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint Daniel of Moscow |
E565334
|
entity |
| Predicate | successor |
P78
|
FINISHED |
| Object | Yuri of Moscow |
—
|
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: Yuri of Moscow | Statement: [Saint Daniel of Moscow, successor, Yuri of Moscow]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yuri of Moscow Context triple: [Saint Daniel of Moscow, successor, Yuri of Moscow]
-
A.
Yuri of Moscow
chosen
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.
-
B.
Yuri of Uglich
Yuri of Uglich was a Russian prince of the early 16th century, known as a younger son of Grand Prince Vasili III and a member of the ruling Rurikid dynasty.
-
C.
Dmitry Urusov
Dmitry Urusov is a Russian nobleman and statesman from the historic Urusov princely family.
-
D.
Ilya
Ilya is a common Russian given name, notably borne by star ice hockey player Ilya Kovalchuk.
-
E.
Юрий
Юрий 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.
- 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_69e24584f9488190bb32730bd2ce023e |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1a5dda7448190b6c686e0db4f4f2f |
completed | April 29, 2026, 6:31 a.m. |
Created at: April 17, 2026, 5:50 p.m.