Triple

T23046921
Position Surface form Disambiguated ID Type / Status
Subject Bhima I E573900 entity
Predicate father P120 FINISHED
Object Durlabharaja 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: Durlabharaja | Statement: [Bhima I, father, Durlabharaja]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Durlabharaja
Context triple: [Bhima I, father, 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. Rajyavardhana
    Rajyavardhana was a 7th-century Indian prince of Thanesar, known as the elder brother of Emperor Harsha and a short-reigned ruler whose death helped precipitate Harsha’s rise to power.
  • D. Durlabhavardhana
    Durlabhavardhana was an early medieval ruler of Kashmir who established the influential Karkota dynasty that dominated the region for several centuries.
  • E. Devagupta
    Devagupta was a monarch of the Later Gupta dynasty, a post-Gupta ruling house in northern India.
  • 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_69e245b9c11481909d06c872214d21af completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f18678e5c48190a96a7b4c9c82f8fe completed April 29, 2026, 4:18 a.m.
Created at: April 17, 2026, 3:54 p.m.