Triple
T26078881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince of Dmitrov |
E657772
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Rus noble 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: Rus noble title Context triple: [Prince of Dmitrov, instanceOf, Rus noble 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.
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.
-
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.
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.
- 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_69ee5bbf0d208190801ee95d4f07fb16 |
completed | April 26, 2026, 6:38 p.m. |
Created at: April 26, 2026, 7:36 p.m.