Triple

T6523002
Position Surface form Disambiguated ID Type / Status
Subject Bhimrao E151230 entity
Predicate hasComponent P35 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: [Bhimrao, hasComponent, Rao]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rao
Context triple: [Bhimrao, hasComponent, 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. Sikandra Rao
    Sikandra Rao is a town in the Braj cultural region of Uttar Pradesh, India, known for its agrarian economy and regional trade.
  • C. Sarvepalli
    Sarvepalli is an Indian surname most prominently associated with Sarvepalli Radhakrishnan, the philosopher and statesman who served as the second President of India.
  • D. Raj
    Raj is the given name of Raj Reddy, a pioneering computer scientist known for his foundational work in artificial intelligence and robotics.
  • E. Swaminathan
    Swaminathan is an Indian surname most prominently associated with M. S. Swaminathan, the agricultural scientist known as the father of India’s Green Revolution.
  • 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_69c687f522748190b3058405553cdabd completed March 27, 2026, 1:36 p.m.
NER Named-entity recognition batch_69c6ad970afc81909d3231203eacf413 completed March 27, 2026, 4:17 p.m.
NED1 Entity disambiguation (via context triple) batch_69c6cb74dfac81908eb44811869450ae completed March 27, 2026, 6:24 p.m.
Created at: March 27, 2026, 1:45 p.m.