Triple
T33979508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Velikaya knyazhna |
E871236
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Russian-language honorific |
C60742
|
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-language honorific Context triple: [Velikaya knyazhna, instanceOf, Russian-language honorific]
-
A.
Russian-language name
A Russian-language name is a personal identifier used in Russian-speaking cultures, typically consisting of a given name, patronymic, and family name, often reflecting linguistic, historical, and cultural traditions of the Russian language.
-
B.
Arabic honorific title
An Arabic honorific title is a formal designation or epithet used to convey respect, status, religious standing, or lineage for an individual within Arabic-speaking and Islamic cultural contexts.
-
C.
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.
-
D.
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.
-
E.
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.
- F. None of above. chosen
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_69f3499da0188190ab1a4ff06fb06a2a |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:50 a.m.