Triple

T4936360
Position Surface form Disambiguated ID Type / Status
Subject Samhita E110820 entity
Predicate partOf P40 FINISHED
Object Yajurveda E19474 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: Yajurveda | Statement: [Samhita, partOf, Yajurveda]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Yajurveda
Context triple: [Samhita, partOf, Yajurveda]
  • A. Yajurveda chosen
    Yajurveda is one of the four principal Vedas of Hinduism, primarily focused on prose mantras and ritual formulas used in sacrificial ceremonies.
  • B. Shukla Yajurveda
    Shukla Yajurveda is one of the two main recensions of the Yajurveda, characterized by its clear separation of mantras and explanatory prose used in Vedic ritual.
  • C. Atharvaveda
    Atharvaveda is one of the four Vedas of Hinduism, comprising hymns, spells, and rituals dealing with everyday life, healing, and protection.
  • D. Jatavedas
    Jatavedas is a prominent Vedic epithet of the fire god Agni, highlighting his all-knowing, all-consuming nature as the divine flame that permeates and witnesses all.
  • E. Krishna Yajurveda
    Krishna Yajurveda is the "Black" recension of the Yajurveda, a Vedic Sanskrit text that intermingles prose mantras and explanatory Brahmana material used primarily in ritual contexts.
  • 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_69bd4415eee08190bdce70276e56a5b4 completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd7085b1dc819099408f6503f0210f completed March 20, 2026, 4:06 p.m.
NED1 Entity disambiguation (via context triple) batch_69bef7e68058819089e179a29ab700bc completed March 21, 2026, 7:56 p.m.
Created at: March 20, 2026, 1:30 p.m.