Triple
T10985607
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elena Ivanovna Diakonova |
E259621
|
entity |
| Predicate | patronymicName |
P7966
|
FINISHED |
| Object | Ivanovna |
E454808
|
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: Ivanovna | Statement: [Elena Ivanovna Diakonova, patronymicName, Ivanovna]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ivanovna Context triple: [Elena Ivanovna Diakonova, patronymicName, Ivanovna]
-
A.
Ivanovna
chosen
Ivanovna is a common Russian patronymic surname suffix for women, indicating "daughter of Ivan."
-
B.
Vasilyevna
Vasilyevna is a Russian female patronymic name indicating that the person's father is named Vasily.
-
C.
Iosifovna
Iosifovna is a Russian patronymic suffix used in female names to indicate that the person's father is named Iosif (Joseph).
-
D.
Ivanova
Ivanova is a common Slavic surname, particularly prevalent in Russia and other Eastern European countries, typically indicating female lineage from someone named Ivan.
-
E.
Maksimovna
Maksimovna is a Russian patronymic derived from the male given name Maksim, traditionally used as a middle name indicating "daughter of Maksim."
- 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_69d6aa895f4c8190887a15460ef622f4 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d787b2e4a88190a81504eee77e2298 |
completed | April 9, 2026, 11:04 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e344d860b08190a035570191c54d7c |
completed | April 18, 2026, 8:46 a.m. |
Created at: April 8, 2026, 9:24 p.m.