Triple
T32580161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khmelnytsky family |
E832759
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Cossack noble family |
C59698
|
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: Cossack noble family Context triple: [Khmelnytsky family, instanceOf, Cossack noble family]
-
A.
medieval Russian noble family
A medieval Russian noble family is a lineage-based social unit of hereditary aristocrats who held land, political influence, and military obligations within the hierarchical structure of Kievan Rus and later principalities.
-
B.
Polish-Lithuanian noble family
A Polish-Lithuanian noble family is a lineage belonging to the historical szlachta estate of the Polish-Lithuanian Commonwealth, characterized by hereditary titles, coats of arms, landholdings, and participation in the region’s political and social life.
-
C.
Georgian noble family
A Georgian noble family is a hereditary lineage from Georgia historically endowed with social prestige, land, and political influence within the country’s aristocratic hierarchy.
-
D.
Ukrainian nobleman
A Ukrainian nobleman is a member of the historical Ukrainian aristocracy, typically landowning and influential in regional politics, culture, and military affairs.
-
E.
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.
- 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_69f349289adc81909f4374a58ec35a39 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 1:04 a.m.