Triple

T22403176
Position Surface form Disambiguated ID Type / Status
Subject Prabhasa Khanda E553812 entity
Predicate associatedWithDeity P1481 FINISHED
Object Skanda 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: Skanda | Statement: [Prabhasa Khanda, associatedWithDeity, Skanda]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Skanda
Context triple: [Prabhasa Khanda, associatedWithDeity, Skanda]
  • A. Kartikeya chosen
    Kartikeya is a Hindu war god, traditionally depicted as a youthful, spear-wielding deity and revered as the son of Shiva and Parvati.
  • B. 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.
  • C. Siva
    Siva is a principal Hindu deity, also known as Shiva, revered as the destroyer and transformer within the Trimurti.
  • D. Ajaya
    Ajaya is an Indian given name, often used for both males and females, meaning "unconquered" or "invincible" in Sanskrit.
  • E. Mayasura
    Mayasura is a legendary architect and king of the Asuras in Hindu mythology, renowned for his extraordinary skill in building magnificent palaces and cities.
  • 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_69e11e4da7048190b4387d422a9a0de5 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f158b565c48190b0f6c19f17995b40 completed April 29, 2026, 1:02 a.m.
Created at: April 16, 2026, 8:46 p.m.