Triple

T686075
Position Surface form Disambiguated ID Type / Status
Subject Ravi River E13285 entity
Predicate mentionedIn P831 FINISHED
Object Rigveda E18873 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: Rigveda | Statement: [Ravi River, mentionedIn, Rigveda]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rigveda
Context triple: [Ravi River, mentionedIn, Rigveda]
  • A. Rigveda chosen
    The Rigveda is the oldest of the four Vedas, a foundational collection of ancient Sanskrit hymns that form a core sacred text of Hinduism.
  • B. Vedas
    The Vedas are a collection of ancient sacred texts composed in Sanskrit that form the foundational spiritual and philosophical scriptures of Hinduism.
  • C. Yajurveda
    Yajurveda is one of the four principal Vedas of Hinduism, primarily focused on prose mantras and ritual formulas used in sacrificial ceremonies.
  • D. Atharvaveda
    Atharvaveda is one of the four Vedas of Hinduism, comprising hymns, spells, and rituals dealing with everyday life, healing, and protection.
  • E. Samaveda
    Samaveda is one of the four Vedas of ancient Indian scripture, primarily consisting of melodies and chants used in Vedic rituals and early Hindu liturgy.
  • 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_69a4933e0f98819097d22766c49b61b8 completed March 1, 2026, 7:27 p.m.
NER Named-entity recognition batch_69a4a0924dec8190bbbd2bb244f85211 completed March 1, 2026, 8:24 p.m.
NED1 Entity disambiguation (via context triple) batch_69a5dca352248190a3e1b4e4c58a1e7f completed March 2, 2026, 6:53 p.m.
Created at: March 1, 2026, 7:36 p.m.