Triple
T3640295
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ivan IV the Terrible |
E77171
|
entity |
| Predicate | patronymicName |
P7966
|
FINISHED |
| Object |
Vasilyevich
Vasilyevich is the Russian patronymic indicating "son of Vasily," famously used in the full name of Ivan IV (Ivan Vasilyevich), the first tsar of Russia.
|
E375781
|
NE FINISHED |
How this triple was built (4 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: Vasilyevich | Statement: [Ivan IV the Terrible, patronymicName, Vasilyevich]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Vasilyevich Context triple: [Ivan IV the Terrible, patronymicName, Vasilyevich]
-
A.
Viktorovich
Viktorovich is a Russian patronymic given name indicating that a person is the son of someone named Viktor.
-
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.
Vasily
Vasily is a masculine given name of Slavic origin, commonly used in Russian-speaking countries.
-
D.
Vasily Vasiliev
Vasily Vasiliev is a descendant of Soviet leader Joseph Stalin’s family line, being the son of Stalin’s son Vasily Stalin.
-
E.
Alekseevich
Alekseevich is a Russian patronymic surname or middle name derived from the given name Aleksey, indicating "son of Aleksey."
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Vasilyevich Triple: [Ivan IV the Terrible, patronymicName, Vasilyevich]
Generated description
Vasilyevich is the Russian patronymic indicating "son of Vasily," famously used in the full name of Ivan IV (Ivan Vasilyevich), the first tsar of Russia.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Vasilyevich Target entity description: Vasilyevich is the Russian patronymic indicating "son of Vasily," famously used in the full name of Ivan IV (Ivan Vasilyevich), the first tsar of Russia.
-
A.
Viktorovich
Viktorovich is a Russian patronymic given name indicating that a person is the son of someone named Viktor.
-
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.
Vasily
Vasily is a masculine given name of Slavic origin, commonly used in Russian-speaking countries.
-
D.
Vasily Vasiliev
Vasily Vasiliev is a descendant of Soviet leader Joseph Stalin’s family line, being the son of Stalin’s son Vasily Stalin.
-
E.
Alekseevich
Alekseevich is a Russian patronymic surname or middle name derived from the given name Aleksey, indicating "son of Aleksey."
- F. None of above. chosen
Provenance (5 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_69ad85dd0be48190b738990cb20c4731 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc32b83188190bfc0ed4dc8f66730 |
completed | March 8, 2026, 6:42 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b44f2a8a5c8190b84dcf4b4b8a939e |
completed | March 13, 2026, 5:53 p.m. |
| NEDg | Description generation | batch_69b45292546c81909770dcd6239dbda3 |
completed | March 13, 2026, 6:08 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69b45f76fcc48190bab9bc6ce83700eb |
completed | March 13, 2026, 7:03 p.m. |
Created at: March 8, 2026, 3:24 p.m.