Triple
T9063637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alekseevich |
E217189
|
entity |
| Predicate | transliteration |
P2508
|
FINISHED |
| Object | Alexeyevich |
E40637
|
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: Alexeyevich | Statement: [Alekseevich, transliteration, Alexeyevich]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Alexeyevich Context triple: [Alekseevich, transliteration, Alexeyevich]
-
A.
Alekseyevich
chosen
Alekseyevich is a Russian patronymic derived from the given name Alexei, indicating "son of Alexei."
-
B.
Alekseevich
Alekseevich is a Russian patronymic surname or middle name derived from the given name Aleksey, indicating "son of Aleksey."
-
C.
Yevgeny
Yevgeny is a masculine given name of Slavic origin, commonly used in Russian-speaking countries.
-
D.
Yermolai Solzhenitsyn
Yermolai Solzhenitsyn is a member of the Solzhenitsyn family, known as one of the sons of Russian writer and dissident Aleksandr Solzhenitsyn.
-
E.
Ignat Solzhenitsyn
Ignat Solzhenitsyn is a Russian-American pianist and conductor, known for his concert performances, recordings, and leadership roles with major orchestras.
- 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_69ca83d5a7f48190b16c1e59bd43ede0 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc94b9f28481909e20366b0e3d14aa |
completed | April 1, 2026, 3:44 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d01798a79081909885a8e61bf04dc3 |
completed | April 3, 2026, 7:40 p.m. |
Created at: March 30, 2026, 7:11 p.m.