Triple

T19721236
Position Surface form Disambiguated ID Type / Status
Subject Bhishmaka E473612 entity
Predicate relatedTo P37 FINISHED
Object Rukmi 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: Rukmi | Statement: [Bhishmaka, relatedTo, Rukmi]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rukmi
Context triple: [Bhishmaka, relatedTo, Rukmi]
  • A. Rukmi chosen
    Rukmi is a character in Hindu mythology known as the proud and antagonistic brother of Rukmini, who opposed her marriage to Krishna.
  • B. Rakcham
    Rakcham is a small Himalayan village in Himachal Pradesh, India, known for its scenic alpine landscapes, traditional Kinnauri culture, and proximity to trekking routes in the Baspa Valley.
  • C. Risha
    Risha is a traditional woven cloth worn by the Dimasa community, typically used as an upper garment or ceremonial attire that reflects their cultural identity and craftsmanship.
  • D. Kaiya
    Kaiya is a feminine given name used in various cultures, often associated with meanings related to the sea, forgiveness, or purity.
  • E. Shuchi
    Shuchi is a relatively obscure figure in Hindu mythology, known primarily as a child of Svaha and thus part of the divine lineage associated with the fire god Agni.
  • 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_69d8e516dd048190a0b6c93ea3e71f58 completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e649f483c481908c6b3114bf9c5934 completed April 20, 2026, 3:44 p.m.
Created at: April 10, 2026, 1:46 p.m.