Triple

T10971201
Position Surface form Disambiguated ID Type / Status
Subject Rotrude E259237 entity
Predicate instanceOf P0 FINISHED
Object Frankish princess C28408 CONCEPT FINISHED

How this triple was built (1 step)

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.

CD Concept disambiguation gpt-5-mini-2025-08-07
Target class: Frankish princess
Context triple: [Rotrude, instanceOf, Frankish princess]
  • A. Ottonian princess
    An Ottonian princess is a noblewoman of the 10th–11th century Ottonian dynasty in the Holy Roman Empire, whose role combined dynastic marriage politics, religious patronage, and the reinforcement of imperial authority.
  • B. Anglo-Norman princess
    An Anglo-Norman princess is a royal woman of the medieval Anglo-Norman dynasty, typically the daughter or close female relative of a king or prince, whose status and marriages were central to political alliances and power dynamics in England and Normandy.
  • C. Bavarian princess
    A Bavarian princess is a noblewoman of royal or princely rank from the historical region of Bavaria, traditionally associated with the Bavarian royal or ruling families.
  • D. princess of France
    A princess of France is a royal woman, typically the daughter or close female relative of a French king or heir, who holds a noble title and plays a ceremonial, dynastic, and sometimes political role within the French monarchy.
  • E. German princess
    A German princess is a female member of a royal or princely family from one of the historical or modern German states, typically holding the title by birth or marriage within the German nobility.
  • F. None of above. chosen

Provenance (1 batch)

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_69d6aa895f4c8190887a15460ef622f4 completed April 8, 2026, 7:20 p.m.
Created at: April 8, 2026, 9:24 p.m.