Triple

T7306609
Position Surface form Disambiguated ID Type / Status
Subject Rath Yatra E167989 entity
Predicate mainDeity P7648 FINISHED
Object Balabhadra E525571 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: Balabhadra | Statement: [Rath Yatra, mainDeity, Balabhadra]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Balabhadra
Context triple: [Rath Yatra, mainDeity, Balabhadra]
  • A. Balabhadra chosen
    Balabhadra, also known as Balarama, is a major Hindu deity revered as the elder brother of Krishna and a prominent figure in Vaishnavism.
  • B. Yudhajit
    Yudhajit is a lesser-known prince in the Ramayana, recognized as the brother of Queen Kaikeyi and thus an uncle of Bharata.
  • C. Mahadeva
    Mahadeva is a principal form of the Hindu god Shiva, revered as the supreme deity and great lord in Shaivism.
  • D. Pradyumna
    Pradyumna is a prominent figure in Hindu mythology, known as the son of Krishna and Rukmini and considered an incarnation of the love god Kamadeva.
  • E. Shanmukha
    Shanmukha is a revered Hindu deity of war and victory, widely worshipped as the six-faced son of Shiva and Parvati.
  • 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_69c6888d8e3c81909db79714903baf31 completed March 27, 2026, 1:39 p.m.
NER Named-entity recognition batch_69c6ebd7dcf88190b3e66bea327fc63d completed March 27, 2026, 8:43 p.m.
NED1 Entity disambiguation (via context triple) batch_69c7eeeaa7488190adb55df8705e0952 completed March 28, 2026, 3:08 p.m.
Created at: March 27, 2026, 3:01 p.m.