Triple
T35021933
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zbyslava of Kiev |
E1010218
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Duchess consort of Poland |
C45009
|
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: Duchess consort of Poland Context triple: [Zbyslava of Kiev, instanceOf, Duchess consort of Poland]
-
A.
Polish royal consort
chosen
A Polish royal consort is the spouse of a reigning Polish monarch who holds a ceremonial and supportive role within the monarchy, often influencing court politics, culture, and dynastic alliances.
-
B.
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.
-
C.
Duchess consort of Austria
The Duchess consort of Austria is the wife of a reigning or titular Duke of Austria, holding the title by marriage and often performing ceremonial, social, and dynastic roles within the Austrian nobility.
-
D.
Polish princess
A Polish princess is a female member of the royal or ruling noble family of Poland, typically holding the title by birth or marriage and often involved in dynastic, political, or cultural affairs of the realm.
-
E.
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.
- 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_69f76dccf0108190af43b465d3750196 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:01 p.m.