Triple
T26328004
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elen ferch Llywarch |
E662307
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Welsh noblewoman |
C51423
|
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: Welsh noblewoman Context triple: [Elen ferch Llywarch, instanceOf, Welsh noblewoman]
-
A.
Welsh noble
A Welsh noble is a member of the traditional aristocracy of Wales, historically holding land, titles, and local authority within the Welsh social and political hierarchy.
-
B.
Scottish noblewoman
A Scottish noblewoman is a woman of high hereditary rank or title in Scotland, often associated with landownership, clan leadership, and participation in the social and political life of the Scottish aristocracy.
-
C.
13th-century English noblewoman
A 13th-century English noblewoman is an aristocratic woman of medieval England who managed estates, forged political and marital alliances, and navigated the social, legal, and religious constraints of feudal society.
-
D.
medieval English noblewoman
A medieval English noblewoman is an aristocratic woman of high social rank in England’s Middle Ages, whose life centers on managing estates, forging political alliances through marriage, and upholding the social, cultural, and religious expectations of the nobility.
-
E.
14th-century English noblewoman
A 14th-century English noblewoman is an aristocratic woman of medieval England who holds social status and influence through birth or marriage, managing estates, patronage, and family alliances within a feudal and patriarchal society.
- F. None of above. chosen
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_69ee812f32748190871d970c4e2a8ddf |
completed | April 26, 2026, 9:18 p.m. |
Created at: April 26, 2026, 10:32 p.m.