Triple
T14495783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yevgeny |
E359493
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Evgeniy |
E359493
|
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: Evgeniy | Statement: [Yevgeny, hasVariant, Evgeniy]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Evgeniy Context triple: [Yevgeny, hasVariant, Evgeniy]
-
A.
Evgeni
Evgeni is a masculine given name most notably associated with Russian-born NHL star Evgeni Malkin.
-
B.
Yevgeny
chosen
Yevgeny is a masculine given name of Slavic origin, commonly used in Russian-speaking countries.
-
C.
Alexey
Alexey is a masculine given name of Slavic origin, commonly used in Russian-speaking countries and derived from the Greek name Alexios, meaning "defender" or "helper."
-
D.
Andrey Voronikhin
Andrey Voronikhin was a prominent Russian neoclassical architect of the late 18th and early 19th centuries, noted for shaping the architectural landscape of St. Petersburg.
-
E.
Vitaly
Vitaly is a masculine given name of Slavic origin, commonly used in Russian-speaking countries.
- 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_69d8279740308190af9df93a3af8592e |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de93109cb081909a6e846db23a4635 |
completed | April 14, 2026, 7:18 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fea59f26188190b81af88940a9c95b |
completed | May 9, 2026, 3:10 a.m. |
Created at: April 10, 2026, 1:21 a.m.