Triple
T21067222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ermentrude of Orléans |
E519008
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Carolingian dynasty consort |
C10093
|
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: Carolingian dynasty consort Context triple: [Ermentrude of Orléans, instanceOf, Carolingian dynasty consort]
-
A.
queen consort of the Franks
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.
Carolingian dynasty member
chosen
A Carolingian dynasty member is an individual belonging to the Frankish royal family that ruled large parts of Western and Central Europe from the 8th to 10th centuries, originating with Charles Martel and reaching its height under Charlemagne.
-
D.
daughter of Charlemagne
A daughter of Charlemagne is a female offspring of the Frankish king and emperor Charlemagne, often used to denote a noblewoman situated within the Carolingian imperial family and its dynastic politics.
-
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.
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_69e0b505ef108190b25dd4033e2ff7eb |
completed | April 16, 2026, 10:08 a.m. |
Created at: April 16, 2026, 2:45 p.m.