Triple
T15100002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Einhard |
E360638
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | FrankishScholar |
C30485
|
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: FrankishScholar Context triple: [Einhard, instanceOf, FrankishScholar]
-
A.
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.
-
B.
Frankish person
chosen
A Frankish person is an individual belonging to the early medieval Germanic people known as the Franks, who inhabited regions of present-day France, Germany, and the Low Countries and played a central role in the formation of Western European kingdoms.
-
C.
Carolingian
Carolingian refers to the dynasty and cultural era in early medieval Western Europe (8th–10th centuries) associated with Charlemagne and his successors, marked by political consolidation, religious reform, and a revival of learning and the arts.
-
D.
Frankish history event
A Frankish history event is a significant occurrence involving the Frankish peoples, kingdoms, or rulers that shaped the political, social, or cultural development of early medieval Western Europe.
-
E.
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.
- 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_69d85a035aa88190b52a139d3a1b7b6d |
completed | April 10, 2026, 2:01 a.m. |
Created at: April 10, 2026, 3:04 a.m.