Triple
T7058167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince Andrei Alexandrovich of Russia |
E164148
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Russian prince |
C20725
|
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 prince Context triple: [Prince Andrei Alexandrovich of Russia, instanceOf, Russian prince]
-
A.
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.
-
B.
Grand Duke of Russia
A Grand Duke of Russia was a male member of the Russian imperial family, typically a son or grandson of a reigning emperor, who held high dynastic rank and status without necessarily exercising sovereign rule.
-
C.
Prussian prince
A Prussian prince is a male royal family member of the Kingdom of Prussia, typically holding hereditary titles, political influence, and social prestige within the Prussian and broader German nobility.
-
D.
Russian grand duchess
A Russian grand duchess is a female member of the Russian imperial family, typically the daughter or granddaughter of a tsar, holding high noble rank and associated with significant social and political status in the Russian Empire.
-
E.
Grand Prince of Moscow
The Grand Prince of Moscow was the medieval ruler of the Grand Duchy of Moscow, who gradually consolidated Russian lands, led resistance against foreign domination, and laid the foundations for a centralized Russian state.
- 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_69c68861678881909961ddf4d779f750 |
completed | March 27, 2026, 1:38 p.m. |
Created at: March 27, 2026, 2:38 p.m.