Triple
T5379936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oleksiy Honcharuk |
E113055
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Oleksiy |
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: Oleksiy | Statement: [Oleksiy Honcharuk, givenName, Oleksiy]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Oleksiy Context triple: [Oleksiy Honcharuk, givenName, Oleksiy]
-
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.
Sergiy
Sergiy is a given name, commonly used as a Ukrainian or Eastern European variant of the name Sergei.
-
D.
Andriy
Andriy is a Slavic given name, equivalent to the English name Andrew.
-
E.
Dmytro
Dmytro is a common Ukrainian male given name, equivalent to "Dmitry" in Russian and derived from the Greek name Demetrios.
- 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_69bd4436a1988190af18dcff7fd306b4 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd86ce56c88190a66b3852416edccb |
completed | March 20, 2026, 5:41 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bf335661c8819091058a5275b95284 |
completed | March 22, 2026, 12:09 a.m. |
Created at: March 20, 2026, 2:03 p.m.