Triple

T22828528
Position Surface form Disambiguated ID Type / Status
Subject Odo of France E565729 entity
Predicate spouse P13 FINISHED
Object Theodrada 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: Theodrada | Statement: [Odo of France, spouse, Theodrada]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Theodrada
Context triple: [Odo of France, spouse, Theodrada]
  • A. Theodrada
    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. Theodrada of Francia chosen
    Theodrada of Francia was a noblewoman of the early Frankish realm, known as a member of the influential Austrasian aristocracy connected to the Carolingian court.
  • E. Etheldreda
    Etheldreda is a feminine given name of Old English origin, historically borne by an Anglo-Saxon saint and queen, and is considered a variant of the name Audrey.
  • 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_69e24585ab1c81909b2b5065d15805d5 completed April 17, 2026, 2:36 p.m.
NER Named-entity recognition batch_69f17e2a0e308190941064965346f890 completed April 29, 2026, 3:42 a.m.
Created at: April 17, 2026, 3:34 p.m.