Triple
T16168182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ilya Danilovich Miloslavsky |
E392361
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Russian boyar |
C9249
|
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 boyar Context triple: [Ilya Danilovich Miloslavsky, instanceOf, Russian boyar]
-
A.
Russian prince
A Russian prince is a male noble of princely rank in Russia, historically belonging to the aristocratic ruling class and often holding political, military, or territorial authority within the Russian Empire or its predecessor states.
-
B.
Russian noblewoman
A Russian noblewoman is an aristocratic woman of the Russian Empire or nobility, typically distinguished by her high social rank, landowning family background, and participation in elite cultural and political life.
-
C.
boyar
chosen
A boyar is a member of the highest rank of the feudal aristocracy in medieval and early modern Eastern Europe, especially in Russia and Romania, second only to the ruling princes or tsars.
-
D.
Bulgarian noble
A Bulgarian noble is a member of the historical aristocratic class in Bulgaria, holding hereditary titles, land, and political influence within the medieval or early modern Bulgarian state.
-
E.
Cossack
A Cossack is a member of a traditionally semi-military, self-governing community from the steppes of Eastern Europe, renowned for their horsemanship, warrior culture, and role in regional defense and expansion.
- 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_69d87f1d32208190942e4e499a80c18c |
completed | April 10, 2026, 4:39 a.m. |
Created at: April 10, 2026, 5:02 a.m.