Triple
T25601618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Knjaz |
E641801
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Slavic 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: Slavic princely title Context triple: [Knjaz, instanceOf, Slavic princely title]
-
A.
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.
-
B.
Slavic ruler
A Slavic ruler is a sovereign leader or monarch from a Slavic people or state, historically responsible for governance, military command, and the administration of justice within their realm.
-
C.
Byzantine noble title
A Byzantine noble title is a formal rank or honorific designation within the hierarchical aristocratic and court system of the Byzantine Empire, signifying status, authority, and often specific administrative or military responsibilities.
-
D.
Rurikid prince
A Rurikid prince is a medieval ruler or dynastic member descended from the Varangian leader Rurik, who governed principalities across Kievan Rus' and its successor states.
-
E.
Polish noble title
A Polish noble title is a hereditary or granted rank within the historical Polish–Lithuanian nobility (szlachta), denoting social status, privileges, and often specific duties in the political and military hierarchy.
- 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_69e75dc60d108190b7e2419e36b0134b |
completed | April 21, 2026, 11:21 a.m. |
Created at: April 21, 2026, 4:31 p.m.