Triple
T32223466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beatrice of Swabia |
E823129
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval German princess |
C13476
|
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: medieval German princess Context triple: [Beatrice of Swabia, instanceOf, medieval German princess]
-
A.
German princess
chosen
A German princess is a female member of a royal or princely family from one of the historical or modern German states, typically holding the title by birth or marriage within the German nobility.
-
B.
13th-century German noblewoman
A 13th-century German noblewoman is an aristocratic woman of the Holy Roman Empire who managed estates, upheld family alliances through marriage, and navigated the social, legal, and religious structures of medieval German nobility.
-
C.
10th-century German noblewoman
A 10th-century German noblewoman was an aristocratic woman in the fragmented realms of the early Holy Roman Empire, whose status, landholdings, and dynastic marriages played key roles in regional power, inheritance, and political alliances.
-
D.
Bavarian princess
A Bavarian princess is a noblewoman of royal or princely rank from the historical region of Bavaria, traditionally associated with the Bavarian royal or ruling families.
-
E.
Carolingian princess
A Carolingian princess is a royal woman of the Carolingian dynasty whose status, marriages, and patronage were central to consolidating political alliances, legitimizing rule, and shaping the cultural and religious life of early medieval Europe.
- 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_69f3490b4f948190b99e4f999f5be25f |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:38 a.m.