Triple

T9921757
Position Surface form Disambiguated ID Type / Status
Subject Rao Bika E187811 entity
Predicate title P38 FINISHED
Object Rao E353796 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: Rao | Statement: [Rao Bika, title, Rao]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rao
Context triple: [Rao Bika, title, Rao]
  • A. Rao chosen
    Rao is a traditional honorific title used by certain Rajput clans in India, historically associated with nobility and local rulership.
  • B. Rajagopala
    Rajagopala is a Hindu deity regarded as a form of Lord Krishna, particularly venerated as the divine cowherd and king of Gokul.
  • C. Sikandra Rao
    Sikandra Rao is a town in the Braj cultural region of Uttar Pradesh, India, known for its agrarian economy and regional trade.
  • D. Sarvepalli
    Sarvepalli is an Indian surname most prominently associated with Sarvepalli Radhakrishnan, the philosopher and statesman who served as the second President of India.
  • E. Kumaraswami
    Kumaraswami is the given name of K. Kamaraj, a prominent Indian independence activist and influential Chief Minister of Tamil Nadu.
  • 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_69ca82b22a688190b52c75bd48429c10 completed March 30, 2026, 2:03 p.m.
NER Named-entity recognition batch_69cdb56abbb88190a21b8b77f1a25b81 completed April 2, 2026, 12:16 a.m.
NED1 Entity disambiguation (via context triple) batch_69d20e019f788190a0106b60c8a39efa completed April 5, 2026, 7:23 a.m.
Created at: March 30, 2026, 8:42 p.m.