Triple
T28025685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Konstantin of Rostov |
E708116
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 13th-century Russian nobility |
C32456
|
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: 13th-century Russian nobility Context triple: [Konstantin of Rostov, instanceOf, 13th-century Russian nobility]
-
A.
16th-century Russian nobility
16th-century Russian nobility were hereditary elites who held land, military and administrative authority, and significant influence at the tsar’s court within the evolving centralized Muscovite state.
-
B.
German-Russian nobleman
A German-Russian nobleman is an aristocrat of German origin or heritage who held social status, land, or titles within the Russian Empire, often serving in its military, administrative, or courtly institutions.
-
C.
Finnish noble
A Finnish noble is a member of the historical aristocratic class in Finland, traditionally holding hereditary titles, land, and social privileges recognized by the Swedish and later Russian crowns, and organized through institutions such as the Finnish House of Nobility.
-
D.
Baltic German noble
A Baltic German noble was a member of the German-speaking hereditary elite in the Baltic provinces (primarily present-day Estonia and Latvia), historically holding significant land, political power, and cultural influence under various ruling empires.
-
E.
medieval European noble
chosen
A medieval European noble is a high-ranking member of the feudal aristocracy who holds land granted by a monarch in exchange for military service and governance over vassals and peasants.
- 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_69ef9b6bdd9c8190bb3a574a03774ad1 |
completed | April 27, 2026, 5:22 p.m. |
Created at: April 27, 2026, 8:12 p.m.