Triple
T36208780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rhys ap Tewdwr |
E1047476
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | King of Deheubarth |
C22154
|
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: King of Deheubarth Context triple: [Rhys ap Tewdwr, instanceOf, King of Deheubarth]
-
A.
king of Deheubarth
chosen
The king of Deheubarth is the sovereign ruler of the medieval Welsh kingdom of Deheubarth, holding supreme political, military, and judicial authority over its territories and people.
-
B.
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.
-
C.
King of Strathclyde
The King of Strathclyde was the monarch of the early medieval Brittonic kingdom of Strathclyde, ruling over the Clyde valley region in what is now southern Scotland and northern England.
-
D.
King of Mann and the Isles
The King of Mann and the Isles was the medieval monarch who ruled the Isle of Man and the surrounding Hebridean islands, exercising maritime power and regional authority between the kingdoms of Scotland, Ireland, and Norway.
-
E.
Duke of Brittany
The Duke of Brittany was the sovereign or semi-sovereign ruler of the historical Duchy of Brittany in western France, holding feudal authority, managing regional governance, and often navigating complex political relations with the French crown and neighboring powers.
- 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_69f76e4214748190a76c986d2a1838c2 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:09 p.m.