Triple
T31095216
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rudolfovich |
E792506
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Russian patronymic given name |
C8491
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Russian patronymic given name Context triple: [Rudolfovich, instanceOf, Russian patronymic given name]
-
A.
Russian patronymic
chosen
A Russian patronymic is a middle name derived from a person's father's given name, typically formed with gendered suffixes to indicate "son of" or "daughter of" in Russian naming conventions.
-
B.
Russian patronymic
A Russian patronymic is a middle name derived from a person's father's given name, modified with gender-specific suffixes to indicate "son of" or "daughter of" in Russian naming conventions.
-
C.
Russian patronymic suffix
A Russian patronymic suffix is a morphological ending added to a parent’s given name to form a middle name indicating a person’s paternal lineage and gender (e.g., -ovich, -evna).
-
D.
Russian surname
A Russian surname is a family name originating from Russian linguistic and cultural traditions, often featuring gendered forms and derived from given names, occupations, places, or personal characteristics.
-
E.
Russian-language surname suffix
A Russian-language surname suffix is a morphological ending attached to a personal name or root that forms a family name and often conveys information about ancestry, gender, or geographic origin.
- F. None of above.
Provenance (1 batch)
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_69f224cf157c81909e2d2bd88c9282c3 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 9:03 p.m.