Triple

T22396239
Position Surface form Disambiguated ID Type / Status
Subject Shani Shingnapur E553637 entity
Predicate hasDeity P5606 FINISHED
Object Lord Shani 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: Lord Shani | Statement: [Shani Shingnapur, hasDeity, Lord Shani]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lord Shani
Context triple: [Shani Shingnapur, hasDeity, Lord Shani]
  • A. Shani chosen
    Shani is a major Hindu deity associated with the planet Saturn, karma, justice, and the dispensation of rewards and hardships.
  • B. Ketu
    Ketu is a bustling residential and commercial neighborhood in Lagos, Nigeria, known for its busy markets, transport hubs, and proximity to major city routes.
  • C. Ketu
    Ketu is one of the nine major astrological bodies in Hindu astrology, regarded as a shadow planet associated with spirituality, karmic lessons, and liberation.
  • D. Shesha
    Shesha is the cosmic serpent in Hindu mythology who serves as the divine couch of Lord Vishnu and symbolizes eternity and the foundation of the universe.
  • E. Shukra (Shukracharya)
    Shukra (Shukracharya) is the revered preceptor and guru of the Asuras in Hindu mythology, renowned for his mastery of divine knowledge and the power to revive the dead.
  • 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_69f1585e84b081908c95ed3e0d987ed8 completed April 29, 2026, 1:01 a.m.
Created at: April 16, 2026, 8:45 p.m.