Triple
T8626771
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viktor Shklovsky |
E204297
|
entity |
| Predicate | patronymicName |
P7966
|
FINISHED |
| Object | Borisovich |
E464290
|
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: Borisovich | Statement: [Viktor Shklovsky, patronymicName, Borisovich]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Borisovich Context triple: [Viktor Shklovsky, patronymicName, Borisovich]
-
A.
Borisovich
chosen
Borisovich is a common Russian patronymic meaning "son of Boris," used as the middle name in many Russian male full names.
-
B.
Semyonov
Semyonov is a common Russian surname borne by numerous notable figures in fields such as literature, science, and military history.
-
C.
Vasily
Vasily is a masculine given name of Slavic origin, commonly used in Russian-speaking countries.
-
D.
Anatoly
Anatoly is a masculine given name of Slavic origin, commonly used in Russian-speaking countries.
-
E.
Akhromeyev
Akhromeyev is the surname of Sergei Akhromeyev, a prominent Soviet military leader and Marshal of the Soviet Union.
- 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_69ca834a4ea0819094970dceb9e389f3 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc472b8fa481909f52f83ea210483e |
completed | March 31, 2026, 10:14 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cebbf918f08190a9b0469eae8e0e0d |
completed | April 2, 2026, 6:56 p.m. |
Created at: March 30, 2026, 6:26 p.m.