Triple

T22073811
Position Surface form Disambiguated ID Type / Status
Subject Pala period E545473 entity
Predicate hasNotablePatron P29285 FINISHED
Object Devapala 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: Devapala | Statement: [Pala period, hasNotablePatron, Devapala]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Devapala
Context triple: [Pala period, hasNotablePatron, 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. Durlabharaja
    Durlabharaja was a medieval Indian ruler, likely a Chaulukya (Solanki) prince or king of Gujarat, known from inscriptions and genealogies of the dynasty.
  • C. Devagupta
    Devagupta was a monarch of the Later Gupta dynasty, a post-Gupta ruling house in northern India.
  • D. Durlabhavardhana
    Durlabhavardhana was an early medieval ruler of Kashmir who established the influential Karkota dynasty that dominated the region for several centuries.
  • E. Bhanudeva I
    Bhanudeva I was a prominent 13th-century king of the Eastern Ganga dynasty in eastern India, known for consolidating royal power and patronizing Hindu temples and culture.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e11e344dfc81909b1d88a7221329c7 completed April 16, 2026, 5:36 p.m.
NER Named-entity recognition batch_69f1288affb081908b64742f7bf467fa completed April 28, 2026, 9:37 p.m.
Created at: April 16, 2026, 8:28 p.m.