Triple
T31020363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brunhild of Austrasia |
E790437
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Visigothic noblewoman |
C35770
|
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: Visigothic noblewoman Context triple: [Brunhild of Austrasia, instanceOf, Visigothic noblewoman]
-
A.
Visigothic queen consort
A Visigothic queen consort is the wife of a reigning Visigothic king, holding a ceremonial and sometimes influential political and religious role within the royal court of the Visigothic Kingdom.
-
B.
Ostrogothic princess
An Ostrogothic princess is a noblewoman of royal lineage within the Ostrogothic kingdom, often serving as a key figure in dynastic alliances, diplomacy, and the preservation of Gothic cultural identity.
-
C.
Ostrogothic queen
An Ostrogothic queen is the royal consort or female sovereign within the Ostrogothic kingdom, wielding political, diplomatic, and often cultural influence in the governance and representation of her Gothic realm.
-
D.
medieval Spanish noblewoman
chosen
A medieval Spanish noblewoman is an aristocratic woman in the Iberian Middle Ages who holds social prestige, land-based wealth, and influence through lineage, marriage alliances, and patronage within a feudal and often courtly setting.
-
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_69f224c811508190a7de096a5b1f5798 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:58 p.m.