Triple

T30235677
Position Surface form Disambiguated ID Type / Status
Subject reign of Muhammad I of Córdoba E768758 entity
Predicate hasSuccessorMonarch P15383 FINISHED
Object al-Mundhir of Córdoba 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: al-Mundhir of Córdoba | Statement: [reign of Muhammad I of Córdoba, hasSuccessorMonarch, al-Mundhir of Córdoba]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasSuccessorMonarch
Context triple: [reign of Muhammad I of Córdoba, hasSuccessorMonarch, al-Mundhir of Córdoba]
  • A. associatedWithSuccessorMonarch
    Indicates that an entity has a relationship or connection specifically with the monarch who succeeds a given monarch in a royal or dynastic line.
  • B. monarchSuccessor chosen
    Indicates that one monarch directly follows another in a royal line of succession.
  • C. successorSovereign
    Indicates that one entity becomes the next ruling sovereign following another entity, inheriting their position of supreme authority.
  • D. successorRuler
    Indicates that one ruler directly follows another in holding a position of authority or rule.
  • E. successorAsCoRulerOf
    Indicates that one entity became the next co-ruler alongside another entity, following a previous co-ruler in a shared rulership 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_69f224820c048190b1435c4cc145acf1 completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69fe031bc6208190860099aef72d8dcb completed May 8, 2026, 3:36 p.m.
PD Predicate disambiguation batch_69fe014c8b388190b5d4e0cb95ee2be5 completed May 8, 2026, 3:29 p.m.
Created at: April 29, 2026, 7:37 p.m.