Triple

T22260834
Position Surface form Disambiguated ID Type / Status
Subject Tarakasura E550218 entity
Predicate killedBy P4646 FINISHED
Object Subrahmanya 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: Subrahmanya | Statement: [Tarakasura, killedBy, Subrahmanya]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Subrahmanya
Context triple: [Tarakasura, killedBy, Subrahmanya]
  • A. Sitarama
    Sitarama is a revered epithet of the Hindu deity Rama that emphasizes his inseparable union with his consort Sita and their ideal of divine marital devotion.
  • B. Rajagopala
    Rajagopala is a Hindu deity regarded as a form of Lord Krishna, particularly venerated as the divine cowherd and king of Gokul.
  • C. Shanmukha chosen
    Shanmukha is a revered Hindu deity of war and victory, widely worshipped as the six-faced son of Shiva and Parvati.
  • D. Nagaraja
    Nagaraja is a title in Hindu and Buddhist traditions referring to a divine serpent king who rules over the nagas and is often associated with protection, water, and the underworld.
  • E. Karpagambal
    Karpagambal is the Hindu goddess Parvati worshipped as the consort of Lord Shiva at the Kapaleeshwarar Temple in Mylapore, Chennai.
  • 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_69e11e42adb8819087714772ea606709 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f141b703b081909a2b432463a8e2df completed April 28, 2026, 11:24 p.m.
Created at: April 16, 2026, 8:39 p.m.