Triple

T33101865
Position Surface form Disambiguated ID Type / Status
Subject Otto I, Duke of Swabia and Bavaria E847072 entity
Predicate successor (Duke of Swabia) P98183 FINISHED
Object Conrad I, Duke of Swabia 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: Conrad I, Duke of Swabia | Statement: [Otto I, Duke of Swabia and Bavaria, successor (Duke of Swabia), Conrad I, Duke of Swabia]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: successor (Duke of Swabia)
Context triple: [Otto I, Duke of Swabia and Bavaria, successor (Duke of Swabia), Conrad I, Duke of Swabia]
  • A. predecessor (Duke of Swabia)
    Indicates that one entity previously held the title of Duke of Swabia immediately before another entity.
  • B. succeededAsDukeOfSwabiaBy chosen
    Indicates that one entity became the next Duke of Swabia following another entity in that title or position.
  • C. successorInLotharingia
    Indicates that one entity is the direct successor of another in ruling or holding authority over Lotharingia.
  • D. successorAsCarolingianRuler
    Indicates that one entity became the next Carolingian ruler directly following another in the line of succession.
  • E. predecessor (Duke of Bavaria)
    Indicates that one entity previously held the title of Duke of Bavaria before another entity.
  • F. None of above.

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_69f3495686508190b76bf20fa5e00bf7 completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69ff7ae5d088819089aa3b6360b6b749 completed May 9, 2026, 6:20 p.m.
PD Predicate disambiguation batch_69ff7a4df6488190bf60d675b36b1d6d completed May 9, 2026, 6:17 p.m.
Created at: May 1, 2026, 1:26 a.m.