Triple
T17419265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alekseyevna |
E423567
|
entity |
| Predicate | transliterationVariant |
P5923
|
FINISHED |
| Object | Alexeyevna |
—
|
NE NERFINISHED |
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: Alexeyevna | Statement: [Alekseyevna, transliterationVariant, Alexeyevna]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Alexeyevna Context triple: [Alekseyevna, transliterationVariant, Alexeyevna]
-
A.
Alekseyevna
chosen
Alekseyevna is a Russian patronymic surname suffix meaning "daughter of Alexei," historically borne by women such as Sophia Alekseyevna of Russia.
-
B.
Alexandrovna
Alexandrovna is a Russian female patronymic indicating "daughter of Alexander," commonly used in the full names of women in Russian nobility and broader Russian culture.
-
C.
Alexeyeva
Alexeyeva is a Russian surname most notably borne by Lyudmila Alexeyeva, a prominent Soviet-era dissident and human rights activist.
-
D.
Anatolyevna
Anatolyevna is a Russian patronymic suffix used for women whose father's given name is Anatoly.
-
E.
Kirillovna
Kirillovna is a Russian female patronymic indicating that the bearer is the daughter of someone named Kirill.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d889d7d27c819088486ce3f0627fa1 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e44234d840819096484a15d407785a |
completed | April 19, 2026, 2:47 a.m. |
Created at: April 10, 2026, 5:46 a.m.