Triple

T23150989
Position Surface form Disambiguated ID Type / Status
Subject Bimbisara E578321 entity
Predicate father P120 FINISHED
Object Bhattiya 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: Bhattiya | Statement: [Bimbisara, father, Bhattiya]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bhattiya
Context triple: [Bimbisara, father, Bhattiya]
  • A. Bhattiya chosen
    Bhattiya was an early ruler in the Haryanka dynasty of Magadha, known primarily from Buddhist and historical traditions as a monarch in the lineage surrounding King Bimbisara.
  • B. Bhandari
    Bhandari is a common South Asian surname, particularly found in Nepal and India, associated with various communities and notable public figures.
  • C. Bhatra
    Bhatra are an indigenous Adivasi community primarily inhabiting the Bastar region of central India, known for their distinct cultural traditions, languages, and agrarian lifestyle.
  • D. Bhati
    Bhati is a prominent Rajput clan historically associated with the rulers of Jaisalmer and parts of northwestern India.
  • E. Bhatt
    Bhatt is an Indian surname commonly found among various communities, including Brahmins and other groups, across regions such as Gujarat and North India.
  • 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_69e245fb8de081908f0eba7b5fd75bc4 completed April 17, 2026, 2:38 p.m.
NER Named-entity recognition batch_69f18ed1a258819091ce86dbd1c51e46 completed April 29, 2026, 4:53 a.m.
Created at: April 17, 2026, 4:01 p.m.