Triple

T22591187
Position Surface form Disambiguated ID Type / Status
Subject Hindu pantheon E564951 entity
Predicate hasDeity P5606 FINISHED
Object Vamana 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: Vamana | Statement: [Hindu pantheon, hasDeity, Vamana]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Vamana
Context triple: [Hindu pantheon, hasDeity, Vamana]
  • A. Vamana chosen
    Vamana is the dwarf Brahmin incarnation of the Hindu god Vishnu, known for subduing the demon king Bali through a request for three strides of land that he then expansively claimed.
  • B. 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.
  • C. Andhaka
    Andhaka is a prominent clan within the ancient Yadava lineage of Hindu tradition, often associated with the family and kingdom of Krishna.
  • D. Anjaneya
    Anjaneya is another name for the Hindu deity Hanuman, revered as a symbol of strength, devotion, and selfless service.
  • E. Surapadman
    Surapadman is a powerful demon king in Hindu mythology, best known as the primary adversary defeated by the god Murugan (Skanda) during the events commemorated in the Skanda Sashti festival.
  • 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_69e245836014819091b91ed3074742a3 completed April 17, 2026, 2:36 p.m.
NER Named-entity recognition batch_69f16160651081909d23735336fd7a16 completed April 29, 2026, 1:39 a.m.
Created at: April 17, 2026, 2:48 p.m.