Triple
T28820063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kyrylo Rozumovsky |
E727737
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Ukrainian nobleman |
C55262
|
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: Ukrainian nobleman Context triple: [Kyrylo Rozumovsky, instanceOf, Ukrainian nobleman]
-
A.
Polish–Lithuanian nobleman
A Polish–Lithuanian nobleman was a member of the szlachta elite of the Polish–Lithuanian Commonwealth, holding hereditary privileges, political rights, and often landed estates within its multiethnic realm.
-
B.
Bohemian nobleman
A Bohemian nobleman is an aristocrat from the historical Kingdom of Bohemia, distinguished by hereditary titles, landownership, and a role in the region’s political and cultural life.
-
C.
Galician nobleman
A Galician nobleman is a member of the hereditary aristocracy originating from the historical region of Galicia, traditionally holding land, titles, and social privileges within its feudal or post-feudal society.
-
D.
Serbian nobleman
A Serbian nobleman is a member of the historical or contemporary Serbian aristocracy, typically holding hereditary titles, land, and social privileges within Serbian society.
-
E.
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.
- 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_69f0319d09088190bbf14cdf1987792a |
completed | April 28, 2026, 4:03 a.m. |
Created at: April 28, 2026, 6:34 a.m.