Triple

T21909586
Position Surface form Disambiguated ID Type / Status
Subject Sanskrit literature E541026 entity
Predicate hasPart P35 FINISHED
Object Raghuvaṃśa 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: Raghuvaṃśa | Statement: [Sanskrit literature, hasPart, Raghuvaṃśa]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Raghuvaṃśa
Context triple: [Sanskrit literature, hasPart, Raghuvaṃśa]
  • A. Raghuvamsha chosen
    Raghuvamsha is the legendary royal lineage in Indian epic tradition to which the hero-king Bharata belongs, celebrated in classical Sanskrit literature and mythology.
  • B. Markandeya
    Markandeya is a revered sage in Hindu tradition, famed for his extraordinary longevity, devotion to Shiva, and visionary accounts of cosmic cycles and deluges.
  • C. Harischandra Upakhyan
    Harischandra Upakhyan is a devotional literary work in the Assamese Vaishnavite tradition, authored by the saint-scholar Srimanta Sankardev.
  • D. Harivamsa
    Harivamsa is an important Sanskrit text traditionally considered an appendix to the Mahabharata, detailing the genealogy, birth, and early life of Krishna.
  • E. Somavamsa
    Somavamsa is a legendary royal lineage in ancient Indian tradition believed to descend from the moon god Chandra.
  • 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_69e0c47c4b9c8190a5586a75f5f36453 completed April 16, 2026, 11:14 a.m.
NER Named-entity recognition batch_69f121d8c3108190a178ec6b3857da3f completed April 28, 2026, 9:08 p.m.
Created at: April 16, 2026, 7:40 p.m.