Triple
T32696374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dmytro Vyshnevetsky |
E836019
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Ukrainian noble |
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 noble Context triple: [Dmytro Vyshnevetsky, instanceOf, Ukrainian noble]
-
A.
Ukrainian nobleman
chosen
A Ukrainian nobleman is a member of the historical Ukrainian aristocracy, typically landowning and influential in regional politics, culture, and military affairs.
-
B.
Lithuanian noble
A Lithuanian noble is a member of the historical aristocratic class of the Grand Duchy of Lithuania (and later the Polish–Lithuanian Commonwealth), holding hereditary titles, land, and political privileges within the region’s feudal and early modern social hierarchy.
-
C.
Muscovite boyar
A Muscovite boyar was a high-ranking noble in medieval and early modern Muscovy who held extensive land, political influence, and advisory roles at the tsar’s court.
-
D.
Ruthenian magnate
A Ruthenian magnate is a powerful noble landowner from the historical Ruthenian (East Slavic) territories, wielding significant political, economic, and social influence within regional aristocratic hierarchies.
-
E.
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.
- 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_69f3493323288190a4e88251035fe96e |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:10 a.m.