Triple
T19708617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Praskovya Fyodorovna Golovina |
E473279
|
entity |
| Predicate | patronymicName |
P7966
|
FINISHED |
| Object | Fyodorovna |
—
|
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: Fyodorovna | Statement: [Praskovya Fyodorovna Golovina, patronymicName, Fyodorovna]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Fyodorovna Context triple: [Praskovya Fyodorovna Golovina, patronymicName, Fyodorovna]
-
A.
Fyodorovna
chosen
Fyodorovna is a Russian patronymic name indicating that a woman is the daughter of someone named Fyodor.
-
B.
Praskovya Fyodorovna
Praskovya Fyodorovna is the self-absorbed and socially preoccupied wife of the dying judge in Leo Tolstoy’s novella "The Death of Ivan Ilyich," embodying the superficiality and moral emptiness of the society around him.
-
C.
Vasilyevna
Vasilyevna is a Russian female patronymic name indicating that the person's father is named Vasily.
-
D.
Mikhailovna
Mikhailovna is a Russian patronymic indicating descent from a father named Mikhail, commonly used as the middle name in female full names.
-
E.
Andreyevna
Andreyevna is a Russian patronymic indicating that a woman is the daughter of a man named Andrey.
- 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_69d8e516dd048190a0b6c93ea3e71f58 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e642bc754481908bdf5bfad069aec8 |
completed | April 20, 2026, 3:14 p.m. |
Created at: April 10, 2026, 1:46 p.m.