Triple

T4782349
Position Surface form Disambiguated ID Type / Status
Subject Uttara Kanda E106395 entity
Predicate featuresCharacter P626 FINISHED
Object Dasharatha E109924 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: Dasharatha | Statement: [Uttara Kanda, featuresCharacter, Dasharatha]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Dasharatha
Context triple: [Uttara Kanda, featuresCharacter, Dasharatha]
  • A. Dasharatha chosen
    Dasharatha is the legendary king of Ayodhya in Hindu mythology, best known as the father of Lord Rama.
  • B. King Ashvapati
    King Ashvapati is a righteous and devoted monarch in the Mahabharata’s Savitrī and Satyavan legend, known especially as Savitrī’s father and a model of piety and wisdom.
  • C. Ramachandra
    Ramachandra, better known as Tatya Tope, was a prominent Indian general and key leader of the 1857 Indian Rebellion against British rule.
  • D. Bhoja
    Bhoja refers to an ancient Indian clan or dynasty traditionally associated with the Yadava lineage and mentioned in various historical and epic sources.
  • E. Dasharatha Maurya
    Dasharatha Maurya was a Mauryan emperor who succeeded Ashoka and ruled a gradually declining empire in the late 3rd century BCE.
  • 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_69bd43f4a9588190bf73e20bc27c03cc completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd65abd0a08190937102c44d102f12 completed March 20, 2026, 3:20 p.m.
NED1 Entity disambiguation (via context triple) batch_69be89cdee488190b810111df56fa1cb completed March 21, 2026, 12:06 p.m.
Created at: March 20, 2026, 1:22 p.m.