Triple

T21319447
Position Surface form Disambiguated ID Type / Status
Subject Balabhadra E525571 entity
Predicate hasAlternativeName P39 FINISHED
Object Balabhadra 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: Balabhadra | Statement: [Balabhadra, hasAlternativeName, Balabhadra]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Balabhadra
Context triple: [Balabhadra, hasAlternativeName, 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. Svayambhudeva
    Svayambhudeva was a notable medieval Jain scholar and poet who composed influential works in the Apabhramsha language.
  • C. Trilochanapala
    Trilochanapala was the final ruler of the Hindu Shahi dynasty in northwestern India, known for his resistance against the early Ghaznavid invasions.
  • D. Vishnukumara
    Vishnukumara was a 10th-century Khmer official associated with the construction and patronage of the intricately carved Banteay Srei temple in Cambodia.
  • E. Manjulabhadra
    Manjulabhadra was an ancient Indian mathematician known for his contributions to early mathematical thought in the Indian subcontinent.
  • 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_69e0b51ad810819098c12392c8e55f6c completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e77ecf12248190bb4172ad7416775e completed April 21, 2026, 1:42 p.m.
Created at: April 16, 2026, 4:38 p.m.