Triple
T2341599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charlemagne |
E45038
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Carolingian dynasty member |
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 member Context triple: [Charlemagne, instanceOf, Carolingian dynasty member]
-
A.
House of Hohenstaufen member
A House of Hohenstaufen member is an individual belonging to the medieval German noble dynasty that produced several Holy Roman Emperors and kings of Germany, Italy, and Sicily between the 12th and 13th centuries.
-
B.
House of Wessex member
A House of Wessex member is an individual belonging to the early medieval royal dynasty that ruled the Anglo-Saxon kingdom of Wessex and later much of England.
-
C.
House of Wittelsbach member
A House of Wittelsbach member is an individual belonging by birth or legitimate adoption to the historic German noble and royal dynasty that ruled territories such as Bavaria and the Palatinate and provided various European kings and emperors.
-
D.
member of the Constantinian dynasty
A member of the Constantinian dynasty is an individual belonging to the imperial family that ruled the Roman Empire from the rise of Constantine the Great in the early 4th century until the death of his descendants later that century.
-
E.
House of Hohenzollern member
A House of Hohenzollern member is an individual belonging by birth or legitimate adoption to the historic German noble and royal dynasty that ruled territories including Brandenburg-Prussia and the German Empire.
- 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_69a88917935081909b755dbf38e81024 |
completed | March 4, 2026, 7:33 p.m. |
Created at: March 4, 2026, 7:52 p.m.