Triple
T30098564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Ban |
E764932
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Arthurian dynasty |
C46899
|
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: Arthurian dynasty Context triple: [House of Ban, instanceOf, Arthurian dynasty]
-
A.
Welsh royal dynasty
chosen
A Welsh royal dynasty is a hereditary ruling family that governed a Welsh kingdom or principality, often claiming descent from legendary or historic native princes and kings.
-
B.
Anglo-Norman dynasty
The Anglo-Norman dynasty was the line of rulers of England, beginning with William the Conqueror after the 1066 Norman Conquest, who combined Norman, French, and Anglo-Saxon influences in medieval English governance and culture.
-
C.
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.
-
D.
medieval English noble dynasty
A medieval English noble dynasty is a powerful hereditary family line that held titles, lands, and political influence across generations in England during the Middle Ages.
-
E.
Anglo-Breton noble
An Anglo-Breton noble is a medieval aristocrat of mixed English and Breton heritage who held land, titles, and political influence across both regions, often serving as a cultural and military intermediary between them.
- 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_69f22474e4288190b5f895fe3974aa92 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:08 p.m.