Triple

T8679219
Position Surface form Disambiguated ID Type / Status
Subject Theobald E205990 entity
Predicate hasVariantForm P457 FINISHED
Object Theudebald E752194 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: Theudebald | Statement: [Theobald, hasVariantForm, Theudebald]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Theudebald
Context triple: [Theobald, hasVariantForm, Theudebald]
  • A. Theodebald chosen
    Theodebald is a variant form of the medieval given name Theobald, historically borne by several Frankish and Germanic nobles and rulers.
  • B. Gundobad
    Gundobad was a powerful Burgundian king and former Roman general who played a key role in the late Western Roman Empire’s politics and later ruled the Burgundian kingdom in Gaul.
  • C. Hilderic
    Hilderic was a 6th-century king of the Vandals in North Africa, noted for his pro-Byzantine policies and relative tolerance toward Catholic Christians.
  • D. Pepin of Landen
    Pepin of Landen was a 7th-century Frankish nobleman and mayor of the palace whose lineage laid the groundwork for the rise of the Carolingian dynasty.
  • E. Hrodebert
    Hrodebert is an ancient Germanic given name meaning "fame-bright" or "bright glory," from which later names like Robert and Roberto are derived.
  • 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_69ca835379688190aa06b9d98e684d58 completed March 30, 2026, 2:06 p.m.
NER Named-entity recognition batch_69cc49f8fa948190a070e90d17b4ede2 completed March 31, 2026, 10:26 p.m.
NED1 Entity disambiguation (via context triple) batch_69cf28748c0c8190a8870650a9b07d7d completed April 3, 2026, 2:39 a.m.
Created at: March 30, 2026, 6:32 p.m.