Triple
T18560950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ovsei-Gershon Aronovich Radomyslsky |
E453636
|
entity |
| Predicate | patronymic |
P7966
|
FINISHED |
| Object |
Aronovich
Aronovich is a Slavic patronymic name meaning "son of Aron," commonly used as a middle name in Russian and related naming traditions.
|
E1329969
|
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: Aronovich | Statement: [Ovsei-Gershon Aronovich Radomyslsky, patronymic, Aronovich]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Aronovich Context triple: [Ovsei-Gershon Aronovich Radomyslsky, patronymic, Aronovich]
-
A.
Romanovich
Romanovich is a Slavic patronymic surname indicating descent from a man named Roman, historically associated with Eastern European nobility such as the rulers of Galicia.
-
B.
Antonovich
Antonovich is the patronymic of Ivan VI of Russia, indicating he was the son of a man named Anton.
-
C.
Arkadi
Arkadi is a masculine given name of Armenian and Slavic origin, commonly used in Eastern Europe and the Caucasus.
-
D.
Anatoly
Anatoly is a masculine given name of Slavic origin, commonly used in Russian-speaking countries.
-
E.
Olgovich
Olgovich is a patronymic surname indicating descent from Oleg, used by members of a medieval Rus' princely lineage.
- 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: Aronovich Triple: [Ovsei-Gershon Aronovich Radomyslsky, patronymic, Aronovich]
Generated description
Aronovich is a Slavic patronymic name meaning "son of Aron," commonly used as a middle name in Russian and related naming traditions.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Aronovich Target entity description: Aronovich is a Slavic patronymic name meaning "son of Aron," commonly used as a middle name in Russian and related naming traditions.
-
A.
Romanovich
Romanovich is a Slavic patronymic surname indicating descent from a man named Roman, historically associated with Eastern European nobility such as the rulers of Galicia.
-
B.
Antonovich
Antonovich is the patronymic of Ivan VI of Russia, indicating he was the son of a man named Anton.
-
C.
Arkadi
Arkadi is a masculine given name of Armenian and Slavic origin, commonly used in Eastern Europe and the Caucasus.
-
D.
Anatoly
Anatoly is a masculine given name of Slavic origin, commonly used in Russian-speaking countries.
-
E.
Olgovich
Olgovich is a patronymic surname indicating descent from Oleg, used by members of a medieval Rus' princely lineage.
- 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_69d8d38974308190a9174430ef256b73 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5380a46f08190afe7ca2ddfe209d5 |
completed | April 19, 2026, 8:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a049ae61fac81909c17b6e9318ed36e |
completed | May 13, 2026, 3:38 p.m. |
| NEDg | Description generation | batch_6a049c6de51c8190ac839784577fa9b7 |
completed | May 13, 2026, 3:44 p.m. |
| NED2 | Entity disambiguation (via description) | batch_6a049d555d208190a729bac48489ed3e |
completed | May 13, 2026, 3:48 p.m. |
Created at: April 10, 2026, 11:42 a.m.