Triple

T18453747
Position Surface form Disambiguated ID Type / Status
Subject Bharata lineage E450850 entity
Predicate namedAfter P63 FINISHED
Object King Bharata 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: King Bharata | Statement: [Bharata lineage, namedAfter, King Bharata]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: King Bharata
Context triple: [Bharata lineage, namedAfter, King Bharata]
  • A. Ramachandra
    Ramachandra, better known as Tatya Tope, was a prominent Indian general and key leader of the 1857 Indian Rebellion against British rule.
  • B. Ramachandra
    Ramachandra is a common Indian male given name of Sanskrit origin, often associated with the Hindu deity Lord Rama.
  • C. King Parikshit
    King Parikshit is a legendary Kuru monarch in Hindu tradition, renowned as the grandson of Arjuna and the central listener of the teachings narrated in the Bhagavata Purana.
  • D. Bharata Chakravartin chosen
    Bharata Chakravartin is a legendary Jain emperor revered as the first universal monarch (chakravartin) and a key figure in early Jain cosmology and mythology.
  • E. Dasharatha
    Dasharatha is the legendary king of Ayodhya in Hindu mythology, best known as the father of Lord Rama.
  • 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_69d8d38345688190b565eac2e4cd7935 completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e5264a49ec8190aa43381d93a55e91 completed April 19, 2026, 7 p.m.
Created at: April 10, 2026, 11:31 a.m.