Triple
T22925239
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yevhen |
E569284
|
entity |
| Predicate | hasSpellingVariant |
P457
|
FINISHED |
| Object | Yevheniy |
—
|
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: Yevheniy | Statement: [Yevhen, hasSpellingVariant, Yevheniy]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yevheniy Context triple: [Yevhen, hasSpellingVariant, Yevheniy]
-
A.
Yevhen
chosen
Yevhen is a masculine given name of Slavic origin, commonly used in Ukraine and other Eastern European countries.
-
B.
Oleksiy
Oleksiy is a common Ukrainian male given name, equivalent to Alexei or Alexey in Russian and Alexius in Latin.
-
C.
Mykola
Mykola is the Ukrainian form of the given name Nicholas, commonly used in Ukraine and among Ukrainian communities.
-
D.
Mykhailo
Mykhailo is a masculine given name of Slavic origin, commonly used in Ukrainian and other Eastern European cultures as a form of Michael.
-
E.
Ihor
Ihor is a Ukrainian given name, commonly considered the Ukrainian form of Igor.
- 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_69e2458f7d008190901dccbaebeaba24 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f180d84fc08190b747c3f9052c657a |
completed | April 29, 2026, 3:54 a.m. |
Created at: April 17, 2026, 3:43 p.m.