Triple

T28945028
Position Surface form Disambiguated ID Type / Status
Subject Lutipri E730555 entity
Predicate instanceOf P0 FINISHED
Object Urartian ruler C24270 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: Urartian ruler
Context triple: [Lutipri, instanceOf, Urartian ruler]
  • A. Germiyanid ruler
    A Germiyanid ruler is a sovereign or prince from the medieval Anatolian beylik of Germiyan, who governed its territories, directed its military and diplomatic affairs, and represented the dynasty’s political authority.
  • B. King of Urartu chosen
    The King of Urartu is the sovereign ruler of the ancient kingdom of Urartu, responsible for governing its territories, commanding its military, overseeing religious and administrative affairs, and representing the state in foreign relations.
  • C. Kayanian king
    A Kayanian king is the sovereign ruler of the ancient Kayanian dynasty, embodying divine authority, martial prowess, and the cultural ideals of his realm.
  • D. Hittite king
    A Hittite king is the supreme political, military, and religious ruler of the Hittite Empire, responsible for governing the state, leading armies, conducting diplomacy, and performing key religious rituals to maintain divine favor and social order.
  • E. Turanian ruler
    A Turanian ruler is a sovereign or leader of the historical or legendary Turanian peoples of Central Eurasia, often depicted in contrast to Iranian or Persian civilizations.
  • F. None of above.

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_69f043ea0aa88190a25acbf46157995a completed April 28, 2026, 5:21 a.m.
Created at: April 28, 2026, 8:39 a.m.