Triple

T38079223
Position Surface form Disambiguated ID Type / Status
Subject Jangchok Cheonwang E950805 entity
Predicate instanceOf P0 FINISHED
Object Dharmapala C22863 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: Dharmapala
Context triple: [Jangchok Cheonwang, instanceOf, Dharmapala]
  • A. Maitraka king
    A Maitraka king is a ruler from the Maitraka dynasty (c. 475–776 CE) that governed the region of Saurashtra and parts of Gujarat in western India, known for their patronage of Buddhism, Jainism, and Hinduism and for maintaining regional power after the decline of the Gupta Empire.
  • B. Pala emperor chosen
    A Pala emperor is a sovereign ruler of the Pala dynasty who governed large parts of the Indian subcontinent, particularly Bengal and Bihar, during the early medieval period, overseeing political administration, military campaigns, and patronage of Buddhism and culture.
  • C. King of Polonnaruwa
    The King of Polonnaruwa is the sovereign ruler of the Polonnaruwa kingdom, responsible for governing its people, overseeing administration, defense, and justice, and serving as the supreme symbol of political and cultural authority.
  • D. Vakataka king
    A Vakataka king is a ruler from the ancient Indian Vakataka dynasty (c. 3rd–5th century CE), known for governing central and southern India and patronizing art, architecture, and literature, including the Ajanta caves.
  • E. King of Nepal
    The King of Nepal was the hereditary monarch and head of state of the Kingdom of Nepal, traditionally regarded as a unifying national figure and symbol of the country's sovereignty until the monarchy's abolition in 2008.
  • 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_69f76f02a6c48190a94f3c0b3ee90cf2 completed May 3, 2026, 3:51 p.m.
Created at: May 3, 2026, 4:21 p.m.