Triple

T23280506
Position Surface form Disambiguated ID Type / Status
Subject Æthelhelm E588846 entity
Predicate givenName P17 FINISHED
Object Æthelhelm 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: Æthelhelm | Statement: [Æthelhelm, givenName, Æthelhelm]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Æthelhelm
Context triple: [Æthelhelm, givenName, Æthelhelm]
  • A. Æthelhelm chosen
    Æ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.
  • 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. Æ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.
  • D. Eadwulf
    Eadwulf was a medieval English ecclesiastic from Crediton, likely a bishop or notable church figure associated with the early Christian history of Devon.
  • E. Æthelbald of Wessex
    Æthelbald of Wessex was a 9th-century king of Wessex and son of King Æthelwulf, known for briefly ruling part of the kingdom during his father's lifetime.
  • 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_69e25d16e2c08190a291de254703129e completed April 17, 2026, 4:17 p.m.
NER Named-entity recognition batch_69f19642b46481909fd455acd2155792 completed April 29, 2026, 5:25 a.m.
Created at: April 17, 2026, 4:55 p.m.