Triple

T4522796
Position Surface form Disambiguated ID Type / Status
Subject Yadu dynasty E103306 entity
Predicate hasNotableMember P304 FINISHED
Object Yadu E102085 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: Yadu | Statement: [Yadu dynasty, hasNotableMember, Yadu]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Yadu
Context triple: [Yadu dynasty, hasNotableMember, Yadu]
  • A. Akrura
    Akrura is a revered figure in Hindu mythology, known as a devout Yadava charioteer and ally of Krishna who played a key role in bringing him to Mathura.
  • B. Yadava chosen
    Yadava refers to the ancient Indo-Aryan clan or community traditionally regarded as the lineage of King Yadu and prominently associated with the Hindu deity Krishna.
  • C. Nandiraj
    Nandiraj is a tributary river that feeds into the Indravati River in central India.
  • D. Pavanputra
    Pavanputra is a revered epithet of the Hindu deity Hanuman, highlighting his divine parentage as the son of the wind god.
  • E. Wiradhuri
    Wiradhuri refers to the Wiradjuri people, one of the largest Aboriginal groups in New South Wales, Australia, known for their rich cultural traditions and strong connection to the land.
  • 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_69bd43dba59881908cf59b31df8c7ae1 completed March 20, 2026, 12:55 p.m.
NER Named-entity recognition batch_69bd574d7c2481909049955ca47613a6 completed March 20, 2026, 2:18 p.m.
NED1 Entity disambiguation (via context triple) batch_69bdd37f7ed48190ae0a82597aafc66e completed March 20, 2026, 11:08 p.m.
Created at: March 20, 2026, 1:02 p.m.