Triple
T20654867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vsevolodovich |
E507596
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | East Slavic patronymic |
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: East Slavic patronymic Context triple: [Vsevolodovich, instanceOf, East Slavic patronymic]
-
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.
Slavic name
A Slavic name is a personal name originating from Slavic languages and cultures, often characterized by specific phonetic patterns, suffixes, and meanings tied to virtues, nature, or heritage.
-
D.
Eastern European surname
An Eastern European surname is a family name originating from countries in Eastern Europe, often reflecting linguistic, geographic, occupational, or patronymic traditions specific to the region.
-
E.
South Slavic surname
A South Slavic surname is a family name originating from South Slavic-speaking regions, often reflecting ancestral occupations, personal traits, or geographic origins and typically following regional linguistic patterns and suffixes.
- 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_69e0b4bf58c081908e52a4500e03ff83 |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:43 a.m.