Triple

T6486648
Position Surface form Disambiguated ID Type / Status
Subject Æthelweard E146528 entity
Predicate sibling P363 FINISHED
Object Ælfthryth E505184 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: Ælfthryth | Statement: [Æthelweard, sibling, Ælfthryth]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ælfthryth
Context triple: [Æthelweard, sibling, Ælfthryth]
  • A. Ælfthryth chosen
    Ælfthryth was a 10th-century English queen consort of King Edgar the Peaceful and a powerful political figure in late Anglo-Saxon England.
  • B. Ælfthryth of Wessex
    Ælfthryth of Wessex was a 9th-century English princess, the daughter of King Alfred the Great, who became queen consort of Mercia through her marriage to Count Baldwin II of Flanders.
  • C. Wulfthryth
    Wulfthryth was a 9th-century Anglo-Saxon noblewoman known primarily as the wife of King Æthelred I of Wessex and a member of the royal house of Wessex.
  • D. Ælfflæd
    Ælfflæd was a 10th-century English noblewoman who became queen consort of the Anglo-Saxon king Edward the Elder.
  • E. Æthelgifu
    Æthelgifu was an Anglo-Saxon noblewoman known primarily as a member of the family of the chronicler and ealdorman Æthelweard.
  • 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_69c6e40c193c8190b4d7acd4530121f0 completed March 27, 2026, 8:09 p.m.
Created at: March 22, 2026, 4:52 p.m.