Triple
T6330984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edward the Elder |
E142379
|
entity |
| Predicate | sibling |
P363
|
FINISHED |
| Object | Æthelweard |
E146528
|
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: Æthelweard | Statement: [Edward the Elder, sibling, Æthelweard]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Æthelweard Context triple: [Edward the Elder, sibling, Æthelweard]
-
A.
Æthelweard
chosen
Æthelweard was a younger son of King Alfred the Great of Wessex and a member of the early English royal family.
-
B.
Æthelmar
Æthelmar was an Anglo-Saxon noble and ecclesiastical patron known for establishing the Benedictine monastery at Eynsham in early 11th-century England.
-
C.
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.
-
D.
Edward the Elder
Edward the Elder was a 10th-century king of the Anglo-Saxons who significantly expanded and consolidated his father's realm, laying foundations for the later kingdom of England.
-
E.
Æthelhelm
Æthelhelm was a 9th-century Anglo-Saxon nobleman, likely a son of King Æthelred I of Wessex and possibly the father of Æthelfrith of Mercia.
- 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_69c008d4d8e88190ad301c05b08722ac |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c06514cbe8819096dbeb17ccb3e3d5 |
completed | March 22, 2026, 9:54 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c640aceaf88190bff029848444e23a |
completed | March 27, 2026, 8:32 a.m. |
Created at: March 22, 2026, 4:30 p.m.