Triple

T31312068
Position Surface form Disambiguated ID Type / Status
Subject Henry III E798489 entity
Predicate instanceOf P0 FINISHED
Object Salian dynasty ruler C58623 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: Salian dynasty ruler
Context triple: [Henry III, instanceOf, Salian dynasty ruler]
  • A. Aulikara dynasty ruler
    An Aulikara dynasty ruler is a monarch from the early medieval Indian Aulikara lineage, governing regions of central India and known primarily through inscriptions and historical records.
  • B. Manghit dynasty ruler
    A Manghit dynasty ruler is a sovereign from the Uzbek Manghit family who governed the Emirate of Bukhara, overseeing its political, military, and religious affairs from the mid-18th to early 20th centuries.
  • C. Habshi dynasty ruler
    A Habshi dynasty ruler is a sovereign of African (often Ethiopian) origin who rose to power in the Indian subcontinent, typically through military or administrative service, and established or led a ruling house known as the Habshi dynasty.
  • D. Injuid dynasty ruler
    An Injuid dynasty ruler is a medieval Persian monarch from the Injuid family who governed parts of Fars and central Iran during the 14th century, overseeing political, military, and administrative affairs.
  • E. Isaurian dynasty ruler
    An Isaurian dynasty ruler is a Byzantine emperor from the 8th–9th century Isaurian line who governed the Eastern Roman Empire and is often associated with initiating and enforcing the policy of iconoclasm.
  • 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_69f224e1932c81908fef14f7b03a10b7 completed April 29, 2026, 3:33 p.m.
Created at: April 29, 2026, 9:15 p.m.