Triple
T10971158
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pepin the Hunchback |
E259236
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Carolingian prince |
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 prince Context triple: [Pepin the Hunchback, instanceOf, Carolingian prince]
-
A.
King of Lotharingia
The King of Lotharingia is the sovereign ruler of the medieval kingdom of Lotharingia, governing its territories, administering justice, leading its armies, and representing its authority within the broader context of the Frankish and later Holy Roman Empire realms.
-
B.
Frankish emperor
A Frankish emperor is a sovereign ruler from the Frankish people who held imperial authority in Western and Central Europe, most notably exemplified by Charlemagne and his successors in the early Middle Ages.
-
C.
King of the Franks
The King of the Franks was the sovereign ruler of the Frankish people and their territories, wielding military, political, and legal authority over the Frankish kingdom in early medieval Europe.
-
D.
King of West Francia
The King of West Francia was the sovereign ruler of the western portion of the former Carolingian Empire, governing the territories that would later evolve into the medieval Kingdom of France.
-
E.
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.
- 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_69d6aa895f4c8190887a15460ef622f4 |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:24 p.m.