Triple
T5583787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oleksiy |
E146702
|
entity |
| Predicate | hasVariantSpelling |
P457
|
FINISHED |
| Object | Oleksij |
E146702
|
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: Oleksij | Statement: [Oleksiy, hasVariantSpelling, Oleksij]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Oleksij Context triple: [Oleksiy, hasVariantSpelling, Oleksij]
-
A.
Oleksiy
chosen
Oleksiy is a common Ukrainian male given name, equivalent to Alexei or Alexey in Russian and Alexius in Latin.
-
B.
Oleksandr
Oleksandr is the Ukrainian form of the given name Alexander, commonly used in Ukraine and among Ukrainian speakers.
-
C.
Volodymyr
Volodymyr is a historic city in western Ukraine known for its medieval heritage and role as a former center of the Volhynia region.
-
D.
Sergiy
Sergiy is a given name, commonly used as a Ukrainian or Eastern European variant of the name Sergei.
-
E.
Roman Danylovych
Roman Danylovych was a 13th-century Ruthenian prince from the ruling dynasty of the Kingdom of Galicia–Volhynia in Eastern Europe.
- 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_69c0090287a08190b4098411effe970c |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c02084b5f0819089b62283c57704ec |
completed | March 22, 2026, 5:01 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c04d2aab348190944cca5375e0ddb9 |
completed | March 22, 2026, 8:12 p.m. |
Created at: March 22, 2026, 3:37 p.m.