Triple

T11162528
Position Surface form Disambiguated ID Type / Status
Subject Conradin E264072 entity
Predicate succeededAsDukeOfSwabiaBy P98183 FINISHED
Object title effectively lapsed LITERAL 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: title effectively lapsed | Statement: [Conradin, succeededAsDukeOfSwabiaBy, title effectively lapsed]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: succeededAsDukeOfSwabiaBy
Context triple: [Conradin, succeededAsDukeOfSwabiaBy, title effectively lapsed]
  • A. reignAsDukeOfBavariaTo
    Indicates that one entity holds and exercises the title and authority of Duke of Bavaria over another entity (typically a territory or domain).
  • B. successorAsHolyRomanEmperor
    Indicates that one entity directly follows another in holding the title of Holy Roman Emperor.
  • C. successorAsKingOfWestFrancia
    Indicates that one person became the next king of West Francia after another person, directly following them in that royal succession.
  • D. reignAsDukeOfBavariaFrom
    Indicates that a person held and exercised the title and authority of Duke of Bavaria starting from a specified time.
  • E. successorAsDukeOfSavoy
    Indicates that one entity became the next Duke of Savoy following another entity in the line of succession.
  • F. None of above. chosen

Provenance (4 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_69d6aa9ccddc8190868998c8b7beb060 completed April 8, 2026, 7:21 p.m.
NER Named-entity recognition batch_69d7e8832fe88190a74d81f9ed547baa completed April 9, 2026, 5:57 p.m.
PD Predicate disambiguation batch_69d75cec26fc8190a5497d186306f935 completed April 9, 2026, 8:01 a.m.
PDg Predicate description generation batch_69d7706116248190a87440bec3960884 completed April 9, 2026, 9:24 a.m.
Created at: April 8, 2026, 9:29 p.m.