Triple

T21886784
Position Surface form Disambiguated ID Type / Status
Subject Mahishasuramardini E540424 entity
Predicate aspectOf P2312 FINISHED
Object Mahadevi 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: Mahadevi | Statement: [Mahishasuramardini, aspectOf, Mahadevi]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mahadevi
Context triple: [Mahishasuramardini, aspectOf, Mahadevi]
  • A. Mahadevi chosen
    Mahadevi is the supreme, all-encompassing form of the Hindu Goddess, embodying and transcending all other goddesses as the ultimate divine feminine.
  • B. Mahadevi
    Mahadevi was a queen consort of the Pala dynasty and the mother of the Pala ruler Mahipala I in medieval Bengal.
  • C. Mahadevi Akka
    Mahadevi Akka was a 12th-century Kannada mystic poet and prominent female saint of the Virashaiva (Lingayat) bhakti movement in southern India.
  • D. Mata Mahadevi
    Mata Mahadevi was the wife of the sixth Sikh Guru, Guru Hargobind, and a respected figure in early Sikh history.
  • E. Maya Devi
    Maya Devi is a Hindu goddess revered as a form of Shakti, particularly worshipped as the presiding deity of Haridwar in Uttarakhand, 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_69e0c47a95908190ae3e19b716accb3d completed April 16, 2026, 11:14 a.m.
NER Named-entity recognition batch_69f118ed35948190bbffba2c40029eee completed April 28, 2026, 8:30 p.m.
Created at: April 16, 2026, 7:05 p.m.