Triple
T15647922
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oleksandr Turchynov |
E376228
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Oleksandr |
E50936
|
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: Oleksandr | Statement: [Oleksandr Turchynov, givenName, Oleksandr]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Oleksandr Context triple: [Oleksandr Turchynov, givenName, Oleksandr]
-
A.
Oleksandr
chosen
Oleksandr is the Ukrainian form of the given name Alexander, commonly used in Ukraine and among Ukrainian speakers.
-
B.
Oleksiy
Oleksiy is a common Ukrainian male given name, equivalent to Alexei or Alexey in Russian and Alexius in Latin.
-
C.
Oleksy
Oleksy is a Polish surname most notably borne by Józef Oleksy, a prominent Polish politician and former Prime Minister.
-
D.
Yevhen
Yevhen is a masculine given name of Slavic origin, commonly used in Ukraine and other Eastern European countries.
-
E.
Sergiy
Sergiy is a given name, commonly used as a Ukrainian or Eastern European variant of the name Sergei.
- 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_69d85cd1564c8190991adda63bfab4b0 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04ed7212c8190be6ff76afa25f7ca |
completed | April 16, 2026, 2:52 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff6ed4d9f88190b7e24bf84c5a916f |
completed | May 9, 2026, 5:28 p.m. |
Created at: April 10, 2026, 4:15 a.m.