Triple
T25530810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elena of Moldavia |
E639904
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Russian grand princess consort |
C44061
|
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 grand princess consort Context triple: [Elena of Moldavia, instanceOf, Russian grand princess consort]
-
A.
Grand Princess consort of Moscow
chosen
The Grand Princess consort of Moscow is the wife of the ruling Grand Prince of Moscow, serving as his principal consort and often playing a significant role in dynastic alliances, court politics, and the cultural life of the Muscovite state.
-
B.
Empress consort of Russia
The Empress consort of Russia was the wife of the reigning Russian emperor (tsar), holding a high ceremonial and social status at court, often influencing politics, culture, and dynastic affairs without ruling in her own right.
-
C.
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.
-
D.
Electress consort
An electress consort is the wife of a ruling prince-elector in the Holy Roman Empire, holding the ceremonial and social status associated with her husband's electoral dignity.
-
E.
Duchess consort of Holstein-Gottorp
The Duchess consort of Holstein-Gottorp is the wife of the reigning Duke of Holstein-Gottorp, holding a ceremonial and dynastic role within the ducal house and its associated European noble networks.
- 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_69e75dbf3f9c8190b3f2a75d1b75d127 |
completed | April 21, 2026, 11:21 a.m. |
Created at: April 21, 2026, 3:14 p.m.