Triple
T22705528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chronicon Æthelweardi |
E561441
|
entity |
| Predicate | author |
P4
|
FINISHED |
| Object | Æthelweard |
—
|
NE NERFINISHED |
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: [Chronicon Æthelweardi, author, Æthelweard]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Æthelweard Context triple: [Chronicon Æthelweardi, author, Æthelweard]
-
A.
Æthelweard
Æthelweard was a younger son of King Alfred the Great of Wessex and a member of the early English royal family.
-
B.
Æthelweard
chosen
Æthelweard was a 10th-century Anglo-Saxon nobleman and Latin-writing historian best known for his chronicle of early English history.
-
C.
Ælfweard of Wessex
Æ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.
-
D.
Æthelswith
Æthelswith was a 9th-century Anglo-Saxon queen of Mercia and daughter of King Æthelwulf of Wessex, known for her role in the political alliances between Wessex and Mercia.
-
E.
Æthelmar
Æthelmar was an Anglo-Saxon noble and ecclesiastical patron known for establishing the Benedictine monastery at Eynsham in early 11th-century England.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e2454f1348819088d83f420925a5c1 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f178cdc93481908f85d04560f8c285 |
completed | April 29, 2026, 3:19 a.m. |
Created at: April 17, 2026, 3:16 p.m.