Triple
T14832425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alekseyev |
E348740
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Alexeyev |
E348740
|
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: Alexeyev | Statement: [Alekseyev, hasVariant, Alexeyev]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Alexeyev Context triple: [Alekseyev, hasVariant, Alexeyev]
-
A.
Alekseyev
chosen
Alekseyev is a Russian surname borne by various notable figures in Russian history, military, and culture.
-
B.
Alekseevich
Alekseevich is a Russian patronymic surname or middle name derived from the given name Aleksey, indicating "son of Aleksey."
-
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.
Alexeyeva
Alexeyeva is a Russian surname most notably borne by Lyudmila Alexeyeva, a prominent Soviet-era dissident and human rights activist.
-
E.
Alexei Aigui
Alexei Aigui is a Russian composer and violinist known for his innovative film scores and contemporary classical music.
- 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_69d822ec69008190a9232caa68836872 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded075af0881908fb35a9e7ee46749 |
completed | April 14, 2026, 11:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe64fc8cdc8190a142a2a3ef889e72 |
completed | May 8, 2026, 10:34 p.m. |
Created at: April 10, 2026, 1:52 a.m.