Triple

T11878760
Position Surface form Disambiguated ID Type / Status
Subject Saibai E282597 entity
Predicate successorAsPrincipalConsort P7964 FINISHED
Object Soyarabai (de facto after Saibai’s death) 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: Soyarabai (de facto after Saibai’s death) | Statement: [Saibai, successorAsPrincipalConsort, Soyarabai (de facto after Saibai’s death)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: successorAsPrincipalConsort
Context triple: [Saibai, successorAsPrincipalConsort, Soyarabai (de facto after Saibai’s death)]
  • A. successorAsQueenConsort chosen
    Indicates that one individual became the next queen consort following another in a royal succession.
  • B. successorAsQueen
    Indicates that one entity became queen directly after another, inheriting the queenship as her successor.
  • C. successorAsPrincessRoyal
    Indicates that one person becomes the next holder of the title "Princess Royal" after another person.
  • D. successorAsRegent
    Indicates that one entity assumes the role of regent following another, serving as their successor in that governing capacity.
  • E. successorAsQueenMother
    Indicates that one individual assumed the role of Queen Mother directly after another individual, succeeding her in that specific position.
  • 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_69d6ab2945d081908a5851c916cbcfb5 completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d8d39d2934819093b9f7006f45e5cb completed April 10, 2026, 10:40 a.m.
PD Predicate disambiguation batch_69d8bb272f88819090c37c944c5a60ab completed April 10, 2026, 8:56 a.m.
Created at: April 8, 2026, 9:44 p.m.