Triple
T28252323
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cwoenthryth |
E712344
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Mercian princess |
C48308
|
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: Mercian princess Context triple: [Cwoenthryth, instanceOf, Mercian princess]
-
A.
Anglo-Saxon royal princess
chosen
An Anglo-Saxon royal princess is a king’s daughter or close female relative in early medieval England, whose status embodies dynastic legitimacy, political alliance, and often religious patronage within the royal household.
-
B.
Saxon princess
A Saxon princess is a noblewoman of royal Saxon lineage, typically characterized by her political significance in dynastic alliances, cultural influence within early medieval Germanic society, and role in consolidating power through marriage and patronage.
-
C.
Lady of the Mercians
The Lady of the Mercians was the title held by Æthelflæd, the powerful early 10th-century ruler of Mercia who led military campaigns and fortified towns while governing in alliance with her brother, King Edward the Elder of Wessex.
-
D.
Ottonian princess
An Ottonian princess is a noblewoman of the 10th–11th century Ottonian dynasty in the Holy Roman Empire, whose role combined dynastic marriage politics, religious patronage, and the reinforcement of imperial authority.
-
E.
Frankish princess
A Frankish princess is a royal woman of the Frankish kingdoms, typically a daughter or close female relative of a Frankish king, whose status and marriages often served to secure political alliances and consolidate dynastic power in early medieval Europe.
- 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_69efb5207eb08190827e4c34048030b1 |
completed | April 27, 2026, 7:12 p.m. |
Created at: April 27, 2026, 11:05 p.m.