Triple
T29146821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dumnonia |
E738795
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical Celtic kingdom |
C53486
|
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: historical Celtic kingdom Context triple: [Dumnonia, instanceOf, historical Celtic kingdom]
-
A.
early medieval Brittonic kingdom
chosen
An early medieval Brittonic kingdom is a politically organized territory in post-Roman Britain ruled by Brittonic-speaking elites, characterized by localized kingship, warrior aristocracies, and a fusion of Roman, Celtic, and emerging Christian traditions.
-
B.
medieval Welsh principality
A medieval Welsh principality is a semi-independent territorial lordship in Wales, ruled by a native prince who exercised political, military, and legal authority within a feudal landscape dominated by competing Welsh dynasties and encroaching English power.
-
C.
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.
-
D.
ancient kingdom
An ancient kingdom is a historically early, centralized state ruled by a monarch, characterized by hierarchical social structures, distinct cultural traditions, and control over defined territories.
-
E.
early medieval kingdom
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.
- 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_69f07cb46f148190874eb8576a447567 |
completed | April 28, 2026, 9:24 a.m. |
Created at: April 28, 2026, 11:40 a.m.