Triple
T2480496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carolingian Empire |
E55803
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Frankish realm |
C7995
|
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 realm Context triple: [Carolingian Empire, instanceOf, Frankish realm]
-
A.
imperial state of the Holy Roman Empire
An imperial state of the Holy Roman Empire was a semi-autonomous political entity—such as a duchy, principality, city, or ecclesiastical territory—directly subject to the authority of the emperor and the imperial diet rather than to any intermediate lord.
-
B.
Anglo-Saxon kingdom
An Anglo-Saxon kingdom is a political entity established in early medieval England by Germanic peoples, characterized by its own monarchy, territorial domain, legal customs, and social hierarchy prior to the Norman Conquest.
-
C.
early medieval kingdom
chosen
An early medieval kingdom is a territorially bounded, monarch-led polity emerging after the fall of the Western Roman Empire, characterized by decentralized power, personal lordship ties, and a fusion of Roman, Germanic, and Christian traditions.
-
D.
Visigothic king
A Visigothic king is the sovereign ruler of the Visigothic people, governing their kingdom’s political, military, legal, and religious affairs in late antiquity and the early Middle Ages.
-
E.
Visigothic king
A Visigothic king is the sovereign ruler of the Visigothic people and their realms, wielding military, judicial, and political authority over their territories in late antiquity and 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_69ab49e670a88190b928e08302381710 |
completed | March 6, 2026, 9:40 p.m. |
Created at: March 6, 2026, 9:45 p.m.