Triple

T4516621
Position Surface form Disambiguated ID Type / Status
Subject Sanjaya E102167 entity
Predicate loyalty P1201 FINISHED
Object Dhritarashtra E103326 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: Dhritarashtra | Statement: [Sanjaya, loyalty, Dhritarashtra]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Dhritarashtra
Context triple: [Sanjaya, loyalty, Dhritarashtra]
  • A. Dhritarashtra chosen
    Dhritarashtra is the blind Kuru king in the Indian epic Mahabharata, whose inner conflict and questions frame the dialogue of the Bhagavad Gita.
  • B. Dhṛtarāṣṭra
    Dhṛtarāṣṭra is one of the Four Heavenly Kings in Buddhist tradition, revered as the guardian of the eastern direction and protector of the Dharma.
  • C. Bhishma
    Bhishma is a revered elder warrior and statesman of the Kuru dynasty in the Indian epic Mahabharata, renowned for his vow of celibacy, unwavering duty, and pivotal role in the Kurukshetra War.
  • D. Drupada
    Drupada is a king in the Indian epic Mahabharata, best known as the ruler of Panchala and the father of Draupadi and Dhrishtadyumna.
  • E. Ugrasena
    Ugrasena is a legendary king in Hindu mythology, known as a ruler of the Yadava clan and the grandfather of Krishna.
  • 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_69bd43d6251c81909deecce3e6e9d69c completed March 20, 2026, 12:55 p.m.
NER Named-entity recognition batch_69bd5726983c8190bca116eeee54241c completed March 20, 2026, 2:18 p.m.
NED1 Entity disambiguation (via context triple) batch_69bdb90b785c81909e76469819f3a487 completed March 20, 2026, 9:15 p.m.
Created at: March 20, 2026, 1:02 p.m.