Triple

T14491191
Position Surface form Disambiguated ID Type / Status
Subject Bhima I E359365 entity
Predicate predecessor P97 FINISHED
Object Durlabharaja E1106962 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: Durlabharaja | Statement: [Bhima I, predecessor, Durlabharaja]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Durlabharaja
Context triple: [Bhima I, predecessor, Durlabharaja]
  • A. Durlabharaja chosen
    Durlabharaja was a medieval Indian ruler, likely a Chaulukya (Solanki) prince or king of Gujarat, known from inscriptions and genealogies of the dynasty.
  • B. Devapala
    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.
  • C. Devagupta
    Devagupta was a monarch of the Later Gupta dynasty, a post-Gupta ruling house in northern India.
  • D. Rajasawardhana
    Rajasawardhana was a ruler associated with the Javanese House of Rajasa, the royal dynasty that founded and led the Singhasari and Majapahit kingdoms in medieval Indonesia.
  • E. Mihirakula
    Mihirakula was a 6th-century Huna ruler in northern India, historically remembered for his military campaigns and reputed cruelty.
  • 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_69d8279740308190af9df93a3af8592e completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de930d820481908b9813014dd02540 completed April 14, 2026, 7:18 p.m.
NED1 Entity disambiguation (via context triple) batch_69fd94a7187c81909f173c2fb70509f5 completed May 8, 2026, 7:45 a.m.
Created at: April 10, 2026, 1:20 a.m.