Triple

T5060934
Position Surface form Disambiguated ID Type / Status
Subject Yudhishthira E114019 entity
Predicate alternativeName P39 FINISHED
Object Dharmaraja E218794 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: Dharmaraja | Statement: [Yudhishthira, alternativeName, Dharmaraja]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Dharmaraja
Context triple: [Yudhishthira, alternativeName, Dharmaraja]
  • A. Dharma-raja chosen
    Dharma-raja is a title of the Hindu god Yama in his role as the divine judge who upholds cosmic law and moral order.
  • B. Dhanadhipati
    Dhanadhipati is an epithet of Kubera, the Hindu god associated with wealth, treasures, and the guardianship of the north.
  • C. Mularaja
    Mularaja was the 10th-century founder of the Chaulukya (Solanki) dynasty in Gujarat, India, known for his patronage of major temples including the famed Somnath Temple.
  • D. Dharma Vira
    Dharma Vira was an Indian civil servant and administrator who held several prominent gubernatorial and diplomatic posts in independent India.
  • E. Angaraja
    Angaraja is an epithet of Karna, the legendary warrior king from the Indian epic Mahabharata renowned for his valor, loyalty, and tragic fate.
  • 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_69bd443c0c8c81908663b77afb28e165 completed March 20, 2026, 12:57 p.m.
NER Named-entity recognition batch_69bd7472a1dc8190942f568a81fdd961 completed March 20, 2026, 4:23 p.m.
NED1 Entity disambiguation (via context triple) batch_69bea49566548190bc6328996789ad9f completed March 21, 2026, 2 p.m.
Created at: March 20, 2026, 1:38 p.m.