Triple
T9422615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Merovingian dynasty |
E227192
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Frankish dynasty |
C18308
|
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 dynasty Context triple: [Merovingian dynasty, instanceOf, Frankish dynasty]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
medieval French dynasty
chosen
A medieval French dynasty is a ruling family that held hereditary power over French territories during the Middle Ages, shaping the kingdom’s political, social, and cultural development through successive generations of monarchs.
-
E.
Frankish historiography
Frankish historiography is the body of historical writing produced in or about the Frankish realms, encompassing chronicles, annals, saints’ lives, and other narratives that construct and interpret the political, religious, and cultural history of the Franks from late antiquity through the early Middle Ages.
- 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_69ca8436ba308190903e470776d2d893 |
completed | March 30, 2026, 2:09 p.m. |
Created at: March 30, 2026, 7:48 p.m.