Triple

T14843058
Position Surface form Disambiguated ID Type / Status
Subject Algar E349014 entity
Predicate hasAlternativeForm P455 FINISHED
Object Ælfgar E1013051 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: Ælfgar | Statement: [Algar, hasAlternativeForm, Ælfgar]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ælfgar
Context triple: [Algar, hasAlternativeForm, Ælfgar]
  • A. Æthelmar
    Æthelmar was an Anglo-Saxon noble and ecclesiastical patron known for establishing the Benedictine monastery at Eynsham in early 11th-century England.
  • B. Ælfgar, Earl of Mercia chosen
    Ælfgar, Earl of Mercia was an 11th-century Anglo-Saxon nobleman and powerful regional ruler in England during the turbulent years leading up to the Norman Conquest.
  • C. Leofwine
    Leofwine was an 11th-century English nobleman and son of Earl Godwin of Wessex, who died fighting alongside his brother King Harold II at the Battle of Hastings in 1066.
  • D. Æ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.
  • E. Oesbern
    Oesbern is a suburban district of the town of Menden in North Rhine-Westphalia, Germany.
  • 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_69d822ec69008190a9232caa68836872 completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69ded28fa49c81908d1059e6cafd607f completed April 14, 2026, 11:49 p.m.
NED1 Entity disambiguation (via context triple) batch_69fe38ab372881909f60435e73424aea completed May 8, 2026, 7:25 p.m.
Created at: April 10, 2026, 1:53 a.m.