Triple
T11138581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Godunov dynasty |
E263479
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Russian ruling house |
C4646
|
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: Russian ruling house Context triple: [Godunov dynasty, instanceOf, Russian ruling house]
-
A.
Russian royalty
chosen
Russian royalty refers to the hereditary ruling families and nobility of Russia, including tsars, emperors, and their extended dynasties, who held political, social, and cultural power from the medieval period until the early 20th century.
-
B.
member of the House of Romanov
A member of the House of Romanov is an individual belonging by birth or marriage to the former imperial dynasty that ruled Russia from 1613 until the abdication of Tsar Nicholas II in 1917.
-
C.
Polish dynasty
A Polish dynasty is a hereditary ruling family originating from Poland that holds political power and influence over the country or its territories across successive generations.
-
D.
Russian grand duchess
A Russian grand duchess is a female member of the Russian imperial family, typically the daughter or granddaughter of a tsar, holding high noble rank and associated with significant social and political status in the Russian Empire.
-
E.
Russian prince
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.
- 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_69d6aa9c0ba08190bbd19c217489b755 |
completed | April 8, 2026, 7:21 p.m. |
Created at: April 8, 2026, 9:28 p.m.