Triple

T5242190
Position Surface form Disambiguated ID Type / Status
Subject Subhadra E118368 entity
Predicate associatedWith P37 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: [Subhadra, associatedWith, Balabhadra]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Balabhadra
Context triple: [Subhadra, associatedWith, 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. 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.
  • D. Shanmukha
    Shanmukha is a revered Hindu deity of war and victory, widely worshipped as the six-faced son of Shiva and Parvati.
  • E. Sureshvara
    Sureshvara was an influential early Advaita Vedanta philosopher and commentator, traditionally regarded as a direct disciple of Adi Shankaracharya and known for his works clarifying non-dualistic doctrine.
  • 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_69bd4467db0881909b3b0982df32cc8f completed March 20, 2026, 12:58 p.m.
NER Named-entity recognition batch_69bd7b4c6fa8819099442b1b110e51fb completed March 20, 2026, 4:52 p.m.
NED1 Entity disambiguation (via context triple) batch_69bf9535f8008190b91cf823e9484b4e completed March 22, 2026, 7:07 a.m.
Created at: March 20, 2026, 1:49 p.m.