Triple

T4522929
Position Surface form Disambiguated ID Type / Status
Subject Kubera E103309 entity
Predicate nameVariant P744 FINISHED
Object Vaisravana E103309 NE FINISHED

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: Vaisravana | Statement: [Kubera, nameVariant, Vaisravana]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Vaisravana
Context triple: [Kubera, nameVariant, Vaisravana]
  • A. Kubera chosen
    Kubera is the Hindu god of wealth and the treasurer of the gods, revered as the lord of riches and prosperity.
  • B. Vajranabha
    Vajranabha is a figure in Hindu tradition regarded as a descendant of Krishna and an early builder or restorer of important Krishna temples such as the Dwarkadhish Temple.
  • C. Indra
    Indra is the king of the gods and lord of storms, war, and the heavens in ancient Vedic and Hindu mythology.
  • D. Vakratunda
    Vakratunda is a revered aspect of the Hindu deity Ganesha, depicted with a curved trunk and associated with the removal of obstacles and the subduing of evil forces.
  • E. Andhaka
    Andhaka is a prominent clan within the ancient Yadava lineage of Hindu tradition, often associated with the family and kingdom of Krishna.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 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_69bd43dba59881908cf59b31df8c7ae1 completed March 20, 2026, 12:55 p.m.
NER Named-entity recognition batch_69bd574d7c2481909049955ca47613a6 completed March 20, 2026, 2:18 p.m.
NED1 Entity disambiguation (via context triple) batch_69bda440e104819095d84fcd183c7a44 completed March 20, 2026, 7:47 p.m.
Created at: March 20, 2026, 1:02 p.m.