Triple
T26961474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elena of Moscow |
E679053
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Rurikid princess |
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: Rurikid princess Context triple: [Elena of Moscow, instanceOf, Rurikid princess]
-
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.
Moldavian princess
A Moldavian princess is a noblewoman of royal or princely rank from the historical principality of Moldavia, often associated with dynastic alliances, courtly life, and regional political influence in Eastern Europe.
-
C.
Lithuanian princess
A Lithuanian princess is a noblewoman of royal or high-ranking lineage from Lithuania, often associated with the country’s medieval Grand Duchy, its cultural heritage, and dynastic alliances.
-
D.
Ottonian princess
An Ottonian princess is a noblewoman of the 10th–11th century Ottonian dynasty in the Holy Roman Empire, whose role combined dynastic marriage politics, religious patronage, and the reinforcement of imperial authority.
-
E.
Mongol princess
A Mongol princess is a high-born woman of the Mongol imperial or noble lineage, whose status, marriages, and political alliances significantly influence tribal unity, diplomacy, and succession within the Mongol realm.
- 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_69eeeb4f3a448190b1e94b2d4776c16e |
completed | April 27, 2026, 4:51 a.m. |
Created at: April 27, 2026, 6:32 a.m.