Triple
T27315785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Athelstan Atheling |
E689342
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Anglo-Saxon royal prince |
C47512
|
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: Anglo-Saxon royal prince Context triple: [Athelstan Atheling, instanceOf, Anglo-Saxon royal prince]
-
A.
Anglo-Saxon royal princess
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.
English prince
An English prince is a male member of the British royal family, typically a son or close male-line descendant of the monarch, who holds the title of "Prince" and may perform ceremonial, diplomatic, and public duties on behalf of the Crown.
-
C.
nobleman of Wessex
chosen
A nobleman of Wessex is a high-ranking landowning aristocrat in the early medieval Anglo-Saxon kingdom of Wessex, holding political, military, and social authority under the king.
-
D.
Anglo-Saxon monarch
An Anglo-Saxon monarch is a hereditary or elected ruler who governed one of the early medieval English kingdoms prior to the Norman Conquest, wielding military, legal, and religious authority over their realm.
-
E.
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.
- 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_69ef355c53a08190a8a92e355a7ce115 |
completed | April 27, 2026, 10:07 a.m. |
Created at: April 27, 2026, 11:30 a.m.