Triple
T1686419
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mikhail |
E36451
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Russian masculine given name |
C90
|
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 masculine given name Context triple: [Mikhail, instanceOf, Russian masculine given name]
-
A.
masculine given name
chosen
A masculine given name is a personal name traditionally assigned to individuals identified as male, often reflecting cultural, historical, or familial significance.
-
B.
Russian patronymic
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.
-
C.
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.
-
D.
English masculine given name
An English masculine given name is a personal first name traditionally used for boys and men in English-speaking cultures, often derived from historical, biblical, or linguistic roots specific to the English language.
-
E.
European given name
A European given name is a personal first name traditionally used in European cultures, often reflecting linguistic, historical, or religious influences specific to a region or country.
- 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_69a886151508819084fa7f1ce6e05577 |
completed | March 4, 2026, 7:20 p.m. |
Created at: March 4, 2026, 7:29 p.m.