Triple

T1548040
Position Surface form Disambiguated ID Type / Status
Subject Pala Empire E33022 entity
Predicate peakUnderRuler P31123 FINISHED
Object Devapala E182277 NE 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: Devapala | Statement: [Pala Empire, peakUnderRuler, Devapala]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Devapala
Context triple: [Pala Empire, peakUnderRuler, Devapala]
  • A. Devapala chosen
    Devapala was a powerful 9th-century ruler of the Pala dynasty in eastern India, known for expanding the empire to its greatest territorial extent and patronizing Buddhism.
  • B. Gopala I
    Gopala I was the founder of the Pala dynasty in eastern India, known for establishing a powerful empire in Bengal and Bihar in the 8th century.
  • C. Rajasuya
    Rajasuya is an ancient Vedic royal consecration ritual performed to legitimize and exalt a king’s sovereignty and supreme status.
  • D. Mahipala I
    Mahipala I was a prominent 11th-century ruler of the Pala dynasty in eastern India, known for reviving the empire’s power and patronizing Buddhism and learning.
  • E. Andhra Bhoja
    Andhra Bhoja is an honorific epithet celebrating Sri Krishnadevaraya as a great patron of Telugu literature and the arts, likening him to the legendary king Bhoja.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69a885ee6db8819099502bc5ce8af881 completed March 4, 2026, 7:20 p.m.
NER Named-entity recognition batch_69aa61ddc9908190a4afca1c24400817 completed March 6, 2026, 5:10 a.m.
NED1 Entity disambiguation (via context triple) batch_69ad719b6c988190a525539d1a29d8d4 completed March 8, 2026, 12:54 p.m.
Created at: March 4, 2026, 7:26 p.m.