Triple
T37248680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eric of Friuli |
E923932
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Carolingian magnate |
C65567
|
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 magnate Context triple: [Eric of Friuli, instanceOf, Carolingian magnate]
-
A.
Frankish prince
A Frankish prince is a male royal of the Frankish realms, typically a son or close male relative of a Frankish king, holding dynastic status, political influence, and often territorial authority within the kingdom.
-
B.
Merovingian ruler
A Merovingian ruler is a king or queen from the Frankish Merovingian dynasty (5th–8th centuries) who exercised political, military, and religious authority over early medieval Gaul and surrounding regions.
-
C.
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.
-
D.
Duke of Lotharingia
The Duke of Lotharingia is a high-ranking noble who governs the historical region of Lotharingia, wielding military, judicial, and administrative authority on behalf of the sovereign.
-
E.
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.
- 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_69f76eaabb4c819093b751b139dad551 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:15 p.m.