Triple
T3549758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daniil Aleksandrovich of Moscow |
E75081
|
entity |
| Predicate | successor |
P78
|
FINISHED |
| Object | Yuri of Moscow |
E324194
|
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: Yuri of Moscow | Statement: [Daniil Aleksandrovich 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: [Daniil Aleksandrovich of Moscow, successor, Yuri of Moscow]
-
A.
Юрий
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.
-
B.
Yuri
Yuri is a common Russian given name, famously borne by Yuri Gagarin, the first human to journey into outer space.
-
C.
Leonid
Leonid is a masculine given name of Slavic origin, notably borne by Soviet leader Leonid Brezhnev.
-
D.
Vasily
Vasily is a masculine given name of Slavic origin, commonly used in Russian-speaking countries.
-
E.
Sergei
Sergei is a masculine given name of Slavic origin, commonly used in Russia and other Eastern European 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_69ad85d33c6c819081d5ac1df13b5680 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbfd38c8c8190a4591689ad57c998 |
completed | March 8, 2026, 6:28 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b589b716648190aeaead138203cbf9 |
completed | March 14, 2026, 4:15 p.m. |
Created at: March 8, 2026, 3:20 p.m.