Triple
T7294240
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vasili II of Moscow |
E164476
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Eastern Orthodox monarch |
C22303
|
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: Eastern Orthodox monarch Context triple: [Vasili II of Moscow, instanceOf, Eastern Orthodox monarch]
-
A.
Eastern European monarch
An Eastern European monarch is a sovereign ruler—such as a king, queen, tsar, or grand duke—who governs or ceremonially represents a state in the Eastern European region, shaped by its distinct historical, cultural, and political traditions.
-
B.
Eastern Orthodox bishop
An Eastern Orthodox bishop is a high-ranking cleric who holds apostolic succession and oversees the spiritual, liturgical, and administrative life of a diocese within the Eastern Orthodox Church.
-
C.
Eastern Roman emperor
An Eastern Roman emperor is the sovereign ruler of the eastern portion of the Roman Empire, later known as the Byzantine Empire, wielding supreme political, military, and religious authority.
-
D.
Tsar of Bulgaria
The Tsar of Bulgaria was the monarchic ruler of the Bulgarian state, holding supreme political and often religious authority over the country during its medieval and modern imperial periods.
-
E.
regent of the Eastern Roman Empire
A regent of the Eastern Roman Empire is an appointed or self-declared authority who governs the empire on behalf of a reigning but underage, absent, incapacitated, or otherwise unable emperor, wielding imperial power without holding the imperial title.
- F. None of above. chosen
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_69c6887a499881909dd23341399c59d8 |
completed | March 27, 2026, 1:39 p.m. |
Created at: March 27, 2026, 3 p.m.