Triple
T15297300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gytha of Wessex |
E365692
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Kievan Rus' royal consort |
C12745
|
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: Kievan Rus' royal consort Context triple: [Gytha of Wessex, instanceOf, Kievan Rus' royal consort]
-
A.
princess of Kievan Rus'
chosen
A princess of Kievan Rus' is a high-born woman of the ruling Rurikid dynasty who played key roles in dynastic alliances, governance, and the cultural and religious life of the medieval East Slavic state.
-
B.
Grand Duchess consort of Lithuania
The Grand Duchess consort of Lithuania is the wife of the reigning Grand Duke of Lithuania, holding a ceremonial and dynastic role within the grand ducal court and state.
-
C.
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.
-
D.
Hungarian queen consort
A Hungarian queen consort is the wife of a reigning king of Hungary, holding the title of queen and performing ceremonial, dynastic, and sometimes political roles without exercising sovereign authority in her own right.
-
E.
Margravine consort of Moravia
A Margravine consort of Moravia is the wife of the ruling margrave of Moravia, holding a ceremonial and often influential position within the region’s medieval or early modern nobility.
- 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_69d85a113ee881908e297a1d38dd79fa |
completed | April 10, 2026, 2:01 a.m. |
Created at: April 10, 2026, 3:15 a.m.