Triple

T21319448
Position Surface form Disambiguated ID Type / Status
Subject Balabhadra E525571 entity
Predicate hasAlternativeName P39 FINISHED
Object Haladhara 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: Haladhara | Statement: [Balabhadra, hasAlternativeName, Haladhara]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Haladhara
Context triple: [Balabhadra, hasAlternativeName, Haladhara]
  • A. Haladhara chosen
    Haladhara is another name for the Hindu deity Balarama, revered as Krishna’s elder brother and famed for wielding the plough as his primary weapon.
  • B. Maheshtala
    Maheshtala is a suburban city near Kolkata in West Bengal, India, known for its rapidly growing residential areas and emerging industrial and commercial development.
  • C. Singhwara
    Singhwara is a town located in the Darbhanga district of the Indian state of Bihar.
  • D. Garudadri
    Garudadri is one of the sacred hills of the Tirumala range, traditionally associated with the divine mount Garuda in Hindu mythology.
  • E. Dashagriva
    Dashagriva is an epithet of the demon-king Ravana from the Hindu epic Ramayana, highlighting his legendary form with ten heads.
  • 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.