Triple

T14491226
Position Surface form Disambiguated ID Type / Status
Subject Mularaja E359366 entity
Predicate nameInScript P77948 FINISHED
Object મૂલરાજ E359366 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: મૂલરાજ | Statement: [Mularaja, nameInScript, મૂલરાજ]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: મૂલરાજ
Context triple: [Mularaja, nameInScript, મૂલરાજ]
  • A. Mularaja chosen
    Mularaja was the 10th-century founder of the Chaulukya (Solanki) dynasty in Gujarat, India, known for his patronage of major temples including the famed Somnath Temple.
  • B. Maharaja Rana
    Maharaja Rana was the hereditary royal title borne by the sovereign rulers of the princely state of Porbandar in pre-independence India.
  • C. Maharaja Wana
    Maharaja Wana is the primary demon-king antagonist in the Malay literary adaptation of the Ramayana, known for abducting Siti Dewi and opposing Seri Rama.
  • D. Maharaja of Panna
    The Maharaja of Panna is the hereditary royal ruler of the former princely state of Panna in central India, traditionally belonging to the Bundela Rajput dynasty.
  • E. Maharaja of Datia
    The Maharaja of Datia was the hereditary ruler of the princely state of Datia in central India, belonging to the Bundela Rajput dynasty.
  • 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_69fd7a404cfc819098a5d6359475a712 completed May 8, 2026, 5:53 a.m.
Created at: April 10, 2026, 1:20 a.m.