Triple
T21599559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yakov Petrovich Golyadkin |
E532998
|
entity |
| Predicate | patronymic |
P7966
|
FINISHED |
| Object | Petrovich |
—
|
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: Petrovich | Statement: [Yakov Petrovich Golyadkin, patronymic, Petrovich]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Petrovich Context triple: [Yakov Petrovich Golyadkin, patronymic, Petrovich]
-
A.
Petrovich
chosen
Petrovich is a Russian patronymic meaning "son of Pyotr (Peter)," commonly used as a middle name in Russian naming conventions.
-
B.
Petrov
Petrov is an alias or alternate name used by Peter P. Peters.
-
C.
Pavlovich
Pavlovich is the Russian patronymic indicating "son of Pavel," used in the full name of Emperor Alexander I of Russia.
-
D.
Petrovsky
Petrovsky is a transliterated Russian surname commonly borne by individuals of Slavic origin and used in various cultural, historical, and geographical contexts.
-
E.
Paveskovich
Paveskovich is a Slavic-origin surname associated with individuals such as John Michael Paveskovich.
- 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_69e0c46364608190a337dc8720dc2a35 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eefae4746c819090afe1d93fe9f175 |
completed | April 27, 2026, 5:57 a.m. |
Created at: April 16, 2026, 6:32 p.m.