Triple
T3000330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boris Pasternak |
E81170
|
entity |
| Predicate | patronymicName |
P7966
|
FINISHED |
| Object | Leonidovich |
E145654
|
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: Leonidovich | Statement: [Boris Pasternak, patronymicName, Leonidovich]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Leonidovich Context triple: [Boris Pasternak, patronymicName, Leonidovich]
-
A.
Leonid
chosen
Leonid is a masculine given name of Slavic origin, notably borne by Soviet leader Leonid Brezhnev.
-
B.
Vladimirovich
Vladimirovich is the Russian patronymic derived from the given name Vladimir, indicating "son of Vladimir" and used in full names such as that of Vladimir Putin.
-
C.
Leontyevich
Leontyevich is a Russian patronymic name derived from the male given name Leonty, traditionally indicating "son of Leonty."
-
D.
Vyacheslav
Vyacheslav is a masculine given name of Slavic origin, most notably borne by Soviet politician Vyacheslav Molotov.
-
E.
Alexandrovich
Alexandrovich is the Russian patronymic indicating "son of Alexander," famously used in the full name of Tsar Nicholas II of Russia.
- 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_69ad8b187fc8819085914d3c9ea3142d |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9a1022e48190afee77db94635ff2 |
completed | March 8, 2026, 3:47 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b12e4b54188190bf900bf10061a57a |
completed | March 11, 2026, 8:56 a.m. |
Created at: March 8, 2026, 2:59 p.m.