Triple

T9119123
Position Surface form Disambiguated ID Type / Status
Subject Yamaloka E218799 entity
Predicate contrastedWith P278 FINISHED
Object Svarga E448833 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: Svarga | Statement: [Yamaloka, contrastedWith, Svarga]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Svarga
Context triple: [Yamaloka, contrastedWith, Svarga]
  • A. Svarga chosen
    Svarga is the heavenly realm in Hindu cosmology, ruled by the god Indra and inhabited by gods and righteous souls.
  • B. Brahmaloka
    Brahmaloka is the highest heavenly realm in Hindu and Buddhist cosmology, associated with the creator deity Brahma and characterized as a plane of great spiritual purity and bliss.
  • C. Varuṇaloka
    Varuṇaloka is the mythological celestial realm associated with the Vedic deity Varuna, often envisioned as his divine oceanic or watery domain.
  • D. Videha
    Videha was an ancient Indo-Aryan kingdom in the eastern Indian subcontinent, centered in the Mithila region and known from Vedic and later religious traditions.
  • E. Parbate
    Parbate is an alternative name for Khas Kura, the historical Indo-Aryan language variety that evolved into modern standard Nepali.
  • 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_69ca83dddd548190983b96c664f7f367 completed March 30, 2026, 2:08 p.m.
NER Named-entity recognition batch_69cca8a7c6d48190a015efd17a017ca1 completed April 1, 2026, 5:10 a.m.
NED1 Entity disambiguation (via context triple) batch_69d047baf5e48190aab0eb19908fabfc completed April 3, 2026, 11:05 p.m.
Created at: March 30, 2026, 7:17 p.m.