Triple
T12790186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Włodzimierz |
E305737
|
entity |
| Predicate | hasEquivalentNameInLanguage |
P63334
|
FINISHED |
| Object |
Uladzimir (Belarusian)
Uladzimir is the Belarusian given name equivalent to the Slavic name Włodzimierz (Vladimir), commonly borne by men in Belarus.
|
E1002780
|
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: Uladzimir (Belarusian) | Statement: [Włodzimierz, hasEquivalentNameInLanguage, Uladzimir (Belarusian)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Uladzimir (Belarusian) Context triple: [Włodzimierz, hasEquivalentNameInLanguage, Uladzimir (Belarusian)]
-
A.
Dmytrii
Dmytrii is a masculine given name of Slavic origin, related to the Greek name Demetrius and commonly used in Eastern European cultures.
-
B.
Branislaŭ Taraškievič
Branislaŭ Taraškievič was a Belarusian linguist and politician best known for codifying the first standard form of the modern Belarusian literary language.
-
C.
Oleksy
Oleksy is a Polish surname most notably borne by Józef Oleksy, a prominent Polish politician and former Prime Minister.
-
D.
Yuriĭ
Yuriĭ is a given name of Slavic origin, commonly used as a variant of the name Yuri.
-
E.
Volha
Volha is the Belarusian variant of the female given name Olga.
- 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: Uladzimir (Belarusian) Triple: [Włodzimierz, hasEquivalentNameInLanguage, Uladzimir (Belarusian)]
Generated description
Uladzimir is the Belarusian given name equivalent to the Slavic name Włodzimierz (Vladimir), commonly borne by men in Belarus.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Uladzimir (Belarusian) Target entity description: Uladzimir is the Belarusian given name equivalent to the Slavic name Włodzimierz (Vladimir), commonly borne by men in Belarus.
-
A.
Dmytrii
Dmytrii is a masculine given name of Slavic origin, related to the Greek name Demetrius and commonly used in Eastern European cultures.
-
B.
Branislaŭ Taraškievič
Branislaŭ Taraškievič was a Belarusian linguist and politician best known for codifying the first standard form of the modern Belarusian literary language.
-
C.
Oleksy
Oleksy is a Polish surname most notably borne by Józef Oleksy, a prominent Polish politician and former Prime Minister.
-
D.
Yuriĭ
Yuriĭ is a given name of Slavic origin, commonly used as a variant of the name Yuri.
-
E.
Volha
Volha is the Belarusian variant of the female given name Olga.
- 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_69d7bdf366888190a8cccb982606889c |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96facb2d48190bc12efc00c9da360 |
completed | April 10, 2026, 9:46 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f68508e4488190bb57a1ade93987ab |
completed | May 2, 2026, 11:13 p.m. |
| NEDg | Description generation | batch_69f687ae18c08190a94dca38bb69d10f |
completed | May 2, 2026, 11:24 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69f68884ed348190a1b2c89b1d655fa9 |
completed | May 2, 2026, 11:28 p.m. |
Created at: April 9, 2026, 5:30 p.m.