Triple
T10538509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yuryev |
E248633
|
entity |
| Predicate | namedAfter |
P63
|
FINISHED |
| Object | Yury (George) |
E97024
|
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: Yury (George) | Statement: [Yuryev, namedAfter, Yury (George)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yury (George) Context triple: [Yuryev, namedAfter, Yury (George)]
-
A.
Georgy
chosen
Georgy is a masculine given name of Russian origin, notably borne by Soviet military commander Georgy Zhukov.
-
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.
Georgy Vinogradov
Georgy Vinogradov was a Soviet-era Russian singer known for his lyrical tenor voice and popular performances of wartime and patriotic songs.
-
D.
Yevgeny
Yevgeny is a masculine given name of Slavic origin, commonly used in Russian-speaking countries.
-
E.
Nikolai Yershov
Nikolai Yershov was a Russian individual notable enough to be commemorated with a grave in Arsk Cemetery in Kazan, Russia.
- 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_69d381c5c7448190bec34bee7ec72bac |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d50a56133c819088285522e64831f7 |
completed | April 7, 2026, 1:44 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d90e5b827881909e87651a88976f18 |
completed | April 10, 2026, 2:51 p.m. |
Created at: April 6, 2026, 12:31 p.m.