Triple

T11013879
Position Surface form Disambiguated ID Type / Status
Subject Fastrada E260311 entity
Predicate relative P37 FINISHED
Object Theodrada E260313 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: Theodrada | Statement: [Fastrada, relative, Theodrada]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Theodrada
Context triple: [Fastrada, relative, Theodrada]
  • A. Theodrada chosen
    Theodrada was a daughter of Charlemagne who became an abbess, likely of the convent at Argenteuil, and lived a religious life within the Carolingian Empire.
  • B. Ermentrud
    Ermentrud is a given name, typically a historical or medieval European female name, that serves as a variant form of Ermintrude.
  • C. Goswintha
    Goswintha was a Visigothic queen consort, known as the influential and often controversial wife of King Leovigild in 6th-century Hispania.
  • D. Himiltrude
    Himiltrude was a Frankish noblewoman, traditionally regarded as Charlemagne’s first partner and the mother of his son Pepin the Hunchback.
  • E. Waldrada
    Waldrada was the controversial noblewoman and long-time mistress of Lothair II, whose relationship with her sparked major political and ecclesiastical disputes in 9th-century Lotharingia.
  • 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_69d6aa9687448190b28d353b1b6a610e completed April 8, 2026, 7:20 p.m.
NER Named-entity recognition batch_69d7978b1e888190b297f107f6021b59 completed April 9, 2026, 12:11 p.m.
NED1 Entity disambiguation (via context triple) batch_69e374c238ac81908e0a5eff958d6545 completed April 18, 2026, 12:10 p.m.
Created at: April 8, 2026, 9:25 p.m.