Triple
T23474294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ulan-Ude |
E570216
|
entity |
| Predicate | formerName |
P65
|
FINISHED |
| Object |
Udinskoye
Udinskoye is the historical name of the Siberian city now known as Ulan-Ude, a major cultural and administrative center in Russia’s Republic of Buryatia.
|
E1588332
|
NE FINISHED |
How this triple was built (4 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: Udinskoye | Statement: [Ulan-Ude, formerName, Udinskoye]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Udinskoye Context triple: [Ulan-Ude, formerName, Udinskoye]
-
A.
Yuzovka
Yuzovka was the original name of the industrial settlement in eastern Ukraine that later developed into the city of Donetsk.
-
B.
Nagurskoye
Nagurskoye is a small Russian military and research settlement located on Alexandra Land in the remote Franz Josef Land archipelago of the Arctic Ocean.
-
C.
Kryukovo
Kryukovo is a railway station and suburban district in Zelenograd, Moscow, serving as a key commuter hub on the Leningradsky suburban rail line.
-
D.
Vladimirovka
Vladimirovka was the original Russian settlement that later developed into the city of Yuzhno-Sakhalinsk on Sakhalin Island in Russia’s Far East.
-
E.
Yasenevo
Yasenevo is a Moscow Metro station serving the Yasenevo District in the south-western part of Moscow, Russia.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Udinskoye Triple: [Ulan-Ude, formerName, Udinskoye]
Generated description
Udinskoye is the historical name of the Siberian city now known as Ulan-Ude, a major cultural and administrative center in Russia’s Republic of Buryatia.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Udinskoye Target entity description: Udinskoye is the historical name of the Siberian city now known as Ulan-Ude, a major cultural and administrative center in Russia’s Republic of Buryatia.
-
A.
Yuzovka
Yuzovka was the original name of the industrial settlement in eastern Ukraine that later developed into the city of Donetsk.
-
B.
Nagurskoye
Nagurskoye is a small Russian military and research settlement located on Alexandra Land in the remote Franz Josef Land archipelago of the Arctic Ocean.
-
C.
Kryukovo
Kryukovo is a railway station and suburban district in Zelenograd, Moscow, serving as a key commuter hub on the Leningradsky suburban rail line.
-
D.
Vladimirovka
Vladimirovka was the original Russian settlement that later developed into the city of Yuzhno-Sakhalinsk on Sakhalin Island in Russia’s Far East.
-
E.
Yasenevo
Yasenevo is a Moscow Metro station serving the Yasenevo District in the south-western part of Moscow, Russia.
- F. None of above. chosen
Provenance (5 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_69e245af8a88819084f2704f6d265a92 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a70363488190bcbdedec5c2a945c |
completed | April 29, 2026, 6:36 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0c82604cc08190b36c6b9636b6bf42 |
completed | May 19, 2026, 3:31 p.m. |
| NEDg | Description generation | batch_6a0ca6f06a348190bfdba0452077f45b |
completed | May 19, 2026, 6:07 p.m. |
| NED2 | Entity disambiguation (via description) | batch_6a0ca7c5176c81908221307bb50ff4ed |
completed | May 19, 2026, 6:11 p.m. |
Created at: April 17, 2026, 6 p.m.