Triple
T13572359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Юрий |
E324194
|
entity |
| Predicate | hasVariantForm |
P457
|
FINISHED |
| Object | Юрій |
E229162
|
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: Юрій | Statement: [Юрий, hasVariantForm, Юрій]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Юрій Context triple: [Юрий, hasVariantForm, Юрій]
-
A.
Yuriĭ
chosen
Yuriĭ is a given name of Slavic origin, commonly used as a variant of the name Yuri.
-
B.
Yevhen
Yevhen is a masculine given name of Slavic origin, commonly used in Ukraine and other Eastern European countries.
-
C.
Vadym
Vadym is a masculine given name of Slavic origin, commonly used in Ukraine and other Eastern European countries.
-
D.
Oleksiy
Oleksiy is a common Ukrainian male given name, equivalent to Alexei or Alexey in Russian and Alexius in Latin.
-
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_69d80769100c819099111274614f5ed2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb0106cb48190b20eb9bda131a68a |
completed | April 12, 2026, 2:45 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f79d3d860c8190a166666a20971de7 |
completed | May 3, 2026, 7:08 p.m. |
Created at: April 9, 2026, 9:48 p.m.