Triple
T30555967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Princess of Borovsk |
E777698
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Russian princely title |
C35099
|
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 princely title Context triple: [Princess of Borovsk, instanceOf, Russian princely title]
-
A.
Russian imperial title
A Russian imperial title is a formal designation of rank and authority within the hierarchy of the Russian Empire, used by monarchs, nobility, and high officials to signify their status and governing roles.
-
B.
Russian imperial title
A Russian imperial title is a formal designation of rank and authority within the hierarchy of the Russian Empire, used by the monarch and members of the ruling dynasty.
-
C.
Ruthenian noble title
A Ruthenian noble title is a hereditary or granted rank of aristocratic status within the historical social and political hierarchy of the Ruthenian (East Slavic) lands.
-
D.
medieval Rus’ title
chosen
A medieval Rus’ title is a formal designation of rank, office, or nobility used in the political and social hierarchy of the East Slavic principalities from roughly the 9th to the 15th centuries.
-
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_69f2249e19108190a458ab446096bf22 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 8:20 p.m.