Triple
T12933697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingdom of Dyfed |
E309448
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | early medieval Welsh kingdom |
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: early medieval Welsh kingdom Context triple: [Kingdom of Dyfed, instanceOf, early medieval Welsh kingdom]
-
A.
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.
-
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.
medieval Welsh ruler
A medieval Welsh ruler is a sovereign or princely leader who governed a Welsh kingdom or territory during the Middle Ages, exercising military, legal, and political authority within a fragmented landscape of competing dynasties and external pressures.
-
D.
Gaelic monarchy
A Gaelic monarchy is a traditional system of kingship found in Gaelic-speaking societies, characterized by hereditary rulers, clan-based power structures, and customary laws governing succession and governance.
-
E.
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.
- 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_69d7bdfa933c8190b5a27aa4a08a19b7 |
completed | April 9, 2026, 2:55 p.m. |
Created at: April 9, 2026, 5:42 p.m.