Triple
T10471346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seven Boyars |
E246929
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Russian noble council |
C8323
|
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 noble council Context triple: [Seven Boyars, instanceOf, Russian noble council]
-
A.
Zemsky Sobor
chosen
Zemsky Sobor was a representative assembly in 16th–17th century Russia, convened by the tsar to consult nobles, clergy, and other estates on major state matters such as succession, legislation, and foreign policy.
-
B.
Russian noblewoman
A Russian noblewoman is an aristocratic woman of the Russian Empire or nobility, typically distinguished by her high social rank, landowning family background, and participation in elite cultural and political life.
-
C.
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.
-
D.
Russian royalty
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.
-
E.
regional legislature of Russia
A regional legislature of Russia is a representative elected body at the subnational (federal subject) level that enacts laws, approves budgets, and oversees executive authorities within its respective region in accordance with the Russian Federation’s constitutional framework.
- 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_69d381c16c248190a2fe5b471e584e9c |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 12:20 p.m.