Triple
T36514029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vladimir Purishkevich |
E899986
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Russian monarchist |
C18961
|
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 monarchist Context triple: [Vladimir Purishkevich, instanceOf, Russian monarchist]
-
A.
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.
-
B.
monarchist figure
chosen
A monarchist figure is an individual who actively supports, symbolizes, or advocates for the preservation or restoration of monarchical rule and its associated traditions.
-
C.
Eastern Orthodox monarch
An Eastern Orthodox monarch is a sovereign ruler whose authority and legitimacy are closely tied to the traditions, theology, and ecclesiastical structures of the Eastern Orthodox Church, often serving as both a political leader and a protector of the faith.
-
D.
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.
-
E.
European royalist politician
A European royalist politician is a political figure in Europe who advocates for the preservation, restoration, or strengthening of a monarchy and its traditional institutions within a given state.
- 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_69f76e5dada881909da2d34bc7a9202a |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:10 p.m.