Triple

T11007497
Position Surface form Disambiguated ID Type / Status
Subject Parmer E260156 entity
Predicate relatedName P3889 FINISHED
Object Parmar E897985 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: Parmar | Statement: [Parmer, relatedName, Parmar]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Parmar
Context triple: [Parmer, relatedName, Parmar]
  • A. Parmar chosen
    Parmar is a surname of Indian origin, commonly associated with various communities and regions in India.
  • B. Yadava
    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. Patidar
    Patidar is a prominent agrarian and mercantile community originating from Gujarat, India, known historically for landownership, farming, and later business and diaspora entrepreneurship.
  • D. Bhonsle
    The Bhonsle were a prominent Maratha royal dynasty best known for producing Chhatrapati Shivaji, founder of the Maratha Empire in western India.
  • E. Parihar
    Parihar is a town in the Sitamarhi district of Bihar, India, known primarily as a local administrative and market center for surrounding rural areas.
  • 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_69d6aa8a6a548190a750f944ccdc8064 completed April 8, 2026, 7:20 p.m.
NER Named-entity recognition batch_69d79757bdcc8190900b267826eece21 completed April 9, 2026, 12:11 p.m.
NED1 Entity disambiguation (via context triple) batch_69e37486b23081909ad282397c50a913 completed April 18, 2026, 12:09 p.m.
Created at: April 8, 2026, 9:25 p.m.