Triple

T18860747
Position Surface form Disambiguated ID Type / Status
Subject Vaishno Mata E461304 entity
Predicate alsoKnownAs P39 FINISHED
Object Mata Rani 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: Mata Rani | Statement: [Vaishno Mata, alsoKnownAs, Mata Rani]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mata Rani
Context triple: [Vaishno Mata, alsoKnownAs, Mata Rani]
  • A. Mata Rani chosen
    Mata Rani is a revered Hindu mother goddess, widely worshipped as Vaishno Devi, whose shrine in the Trikuta Mountains near Katra is one of India’s most important pilgrimage destinations.
  • B. Mangalambika
    Mangalambika is a Hindu goddess revered as the consort of Lord Shiva at the Adi Kumbeswarar Temple in Kumbakonam, Tamil Nadu.
  • C. Rajasbai
    Rajasbai was a queen consort of the Maratha Empire, known primarily as one of the wives of Chhatrapati Rajaram I.
  • D. Rukmini
    Rukmini is a principal queen of the Hindu god Krishna, revered as an incarnation of the goddess Lakshmi and celebrated for her devotion and role in Krishna’s life.
  • E. Maharani
    Maharani is a Sanskrit-derived royal title used in South Asia for a queen or the wife of a maharaja, often signifying a high-ranking female ruler or consort.
  • 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_69d8dcfb7b9c8190854e7b171b98ea2e completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5c060bfc4819092ac591692a6ccd5 completed April 20, 2026, 5:57 a.m.
Created at: April 10, 2026, 11:57 a.m.