Triple
T13825697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hildegard of Vinzgouw |
E332242
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Frankish queen consort |
C28407
|
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: Frankish queen consort Context triple: [Hildegard of Vinzgouw, instanceOf, Frankish queen consort]
-
A.
queen consort of the Franks
chosen
A queen consort of the Franks is the wife of a reigning Frankish king, holding ceremonial, dynastic, and often political influence without ruling in her own right.
-
B.
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.
-
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.
Bavarian queen consort
A Bavarian queen consort is the wife of a reigning king of Bavaria, holding the ceremonial and social role of queen without exercising sovereign authority.
-
E.
Holy Roman Empress consort
A Holy Roman Empress consort is the wife of a reigning Holy Roman Emperor, holding the empire’s highest female title and often exercising ceremonial, dynastic, and sometimes political influence within the Holy Roman Empire.
- 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_69d81c5ae7c88190b0dd41bdafeb5999 |
completed | April 9, 2026, 9:38 p.m. |
Created at: April 9, 2026, 10:13 p.m.