Triple
T38205469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Godepert |
E1009188
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Agilolfing dynasty member |
C61110
|
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: Agilolfing dynasty member Context triple: [Godepert, instanceOf, Agilolfing dynasty member]
-
A.
member of the Agilolfing dynasty
chosen
A member of the Agilolfing dynasty is an individual belonging to the early medieval noble family that ruled Bavaria and parts of neighboring regions in the 6th to 8th centuries.
-
B.
Carolingian dynasty member
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.
-
C.
Ottonian dynasty member
An Ottonian dynasty member is an individual belonging to the German royal and imperial family that ruled the East Frankish (German) kingdom and Holy Roman Empire from the early 10th to early 11th centuries, beginning with Henry the Fowler and most prominently represented by Otto I, Otto II, and Otto III.
-
D.
member of the Ludovingian dynasty
A member of the Ludovingian dynasty is an individual belonging to the medieval German noble house that ruled Thuringia and held significant influence in the Holy Roman Empire from the 11th to 13th centuries.
-
E.
ancestor of the Carolingian dynasty
A foundational progenitor whose lineage directly leads to the rulers of the Carolingian dynasty, providing the bloodline and early power base from which the dynasty emerged.
- 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_69f76dc94fcc8190bd2f55e81f9d6527 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:30 p.m.