Triple
T6642693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Athelstan |
E150624
|
entity |
| Predicate | relative |
P37
|
FINISHED |
| Object | Ælfweard of Wessex |
E594255
|
NE FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Ælfweard of Wessex | Statement: [Athelstan, relative, Ælfweard of Wessex]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ælfweard of Wessex Context triple: [Athelstan, relative, Ælfweard of Wessex]
-
A.
Ælfweard of Wessex
chosen
Ælfweard of Wessex was a short-lived early 10th-century Anglo-Saxon prince who briefly claimed the English throne as the son of King Edward the Elder.
-
B.
Eadwulf of Crediton
Eadwulf of Crediton was an early medieval English bishop who served as the inaugural head of the Diocese of Crediton in Devon.
-
C.
Æthelweard
Æthelweard was a 10th-century Anglo-Saxon nobleman and Latin-writing historian best known for his chronicle of early English history.
-
D.
Æthelweard
Æthelweard was a younger son of King Alfred the Great of Wessex and a member of the early English royal family.
-
E.
Egbert of Wessex
Egbert of Wessex was a 9th-century king who significantly expanded West Saxon power and laid foundations for the later unification of England.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 batches)
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_69c687f1a3048190828b7342f7125d5c |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6aff749d48190bf24d448daf13bc7 |
completed | March 27, 2026, 4:27 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c6f7944bdc81909ea991062dce619d |
completed | March 27, 2026, 9:33 p.m. |
Created at: March 27, 2026, 2 p.m.