Triple
T6486663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Æthelweard |
E146528
|
entity |
| Predicate | relative |
P37
|
FINISHED |
| Object | Eadwig |
E171724
|
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: Eadwig | Statement: [Æthelweard, relative, Eadwig]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Eadwig Context triple: [Æthelweard, relative, Eadwig]
-
A.
Eadwig of England
chosen
Eadwig of England was a 10th-century king of the English whose short and turbulent reign was marked by political conflict with powerful nobles and church leaders.
-
B.
Ethelred
Ethelred was a medieval Scottish churchman who served as Abbot of Dunkeld, an important religious and political center in early Scotland.
-
C.
Eadred of England
Eadred of England was a 10th-century king of the English from the House of Wessex who consolidated royal authority over Northumbria and helped secure the unification of England.
-
D.
Æthelweard
Æthelweard was a 10th-century Anglo-Saxon nobleman and Latin-writing historian best known for his chronicle of early English history.
-
E.
Æthelweard
Æthelweard was a younger son of King Alfred the Great of Wessex and a member of the early English royal family.
- 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_69c0090158c08190af0df9a2348d2d52 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c06a706d4c8190b7a3cc8855abcecb |
completed | March 22, 2026, 10:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c70060c7788190aab7ca88615d6e71 |
completed | March 27, 2026, 10:10 p.m. |
Created at: March 22, 2026, 4:52 p.m.