Triple
T17833113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Praskovia Ivanovna of Russia |
E445311
|
entity |
| Predicate | patronymicName |
P7966
|
FINISHED |
| Object | Ivanovna |
—
|
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: Ivanovna | Statement: [Praskovia Ivanovna of Russia, patronymicName, Ivanovna]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ivanovna Context triple: [Praskovia Ivanovna of Russia, 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.
Stepanida Ivanovna
Stepanida Ivanovna is known primarily as the mother of Irina Godunova, the wife of Tsar Feodor I of Russia and sister of Tsar Boris Godunov.
-
E.
Mikhailovna
Mikhailovna is a Russian patronymic indicating descent from a father named Mikhail, commonly used as the middle name in female full names.
- 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_69d8b9f1a6d881909f024bc603111cdb |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e48d257414819088730f48ad7ab9ae |
completed | April 19, 2026, 8:07 a.m. |
Created at: April 10, 2026, 10:15 a.m.