Triple
T31393621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amalafrida |
E800802
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Ostrogothic princess |
C57512
|
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: Ostrogothic princess Context triple: [Amalafrida, instanceOf, Ostrogothic princess]
-
A.
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.
-
B.
Lombard princess
A Lombard princess is a noblewoman of royal blood from the Lombard kingdoms of early medieval Italy, often serving as a key figure in dynastic alliances, courtly politics, and the transmission of cultural and religious influence.
-
C.
Frankish princess
A Frankish princess is a royal woman of the Frankish kingdoms, typically a daughter or close female relative of a Frankish king, whose status and marriages often served to secure political alliances and consolidate dynastic power in early medieval Europe.
-
D.
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.
-
E.
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.
- F. None of above. chosen
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_69f224e9d7048190b0cc20f9071bd3e4 |
completed | April 29, 2026, 3:34 p.m. |
Created at: April 29, 2026, 9:19 p.m.