Triple
T20990734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tymofiy Mylovanov |
E517016
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Tymofiy |
—
|
NE NERFINISHED |
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: Tymofiy | Statement: [Tymofiy Mylovanov, givenName, Tymofiy]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tymofiy Context triple: [Tymofiy Mylovanov, givenName, Tymofiy]
-
A.
Tymofiy
chosen
Tymofiy is a masculine given name of Ukrainian origin, notably borne by economist and former Ukrainian minister Tymofiy Mylovanov.
-
B.
Vadym
Vadym is a masculine given name of Slavic origin, commonly used in Ukraine and other Eastern European countries.
-
C.
Ihor
Ihor is a Ukrainian given name, commonly considered the Ukrainian form of Igor.
-
D.
Vasyl
Vasyl is a common Ukrainian male given name, equivalent to Basil in English.
-
E.
Oleksy
Oleksy is a Polish surname most notably borne by Józef Oleksy, a prominent Polish politician and former Prime Minister.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b4ffac148190bbade9f0eceb660b |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6fc1ba3d0819080d9d03817a45026 |
completed | April 21, 2026, 4:24 a.m. |
Created at: April 16, 2026, 1:49 p.m.