Triple
T15233235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andrey Bogolyubsky |
E364057
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval Russian noble |
C20725
|
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: medieval Russian noble Context triple: [Andrey Bogolyubsky, instanceOf, medieval Russian noble]
-
A.
Russian prince
chosen
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.
medieval European noble
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.
-
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.
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.
- 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_69d85a0ce24c81909c4d3b6475548c95 |
completed | April 10, 2026, 2:01 a.m. |
Created at: April 10, 2026, 3:12 a.m.