Triple

T2640367
Position Surface form Disambiguated ID Type / Status
Subject Mewar E62850 entity
Predicate hasMajorCity P316 FINISHED
Object Dungarpur E232589 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: Dungarpur | Statement: [Mewar, hasMajorCity, Dungarpur]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Dungarpur
Context triple: [Mewar, hasMajorCity, Dungarpur]
  • A. Dungarpur State chosen
    Dungarpur State was a princely state in western India, historically ruled by Rajput chiefs and later integrated into the modern state of Rajasthan.
  • B. Banswara State
    Banswara State was a princely state in what is now Rajasthan, India, historically ruled by Rajput chiefs and later integrated into the Indian Union after independence.
  • C. Bhilwara
    Bhilwara is a prominent industrial city in the Indian state of Rajasthan, known especially for its large textile and garment manufacturing sector.
  • D. Dholpur
    Dholpur is a city in the Indian state of Rajasthan, known for its red sandstone, historical forts, and location near the Chambal ravines.
  • E. Shahdol
    Shahdol is a city in the eastern part of Madhya Pradesh, India, known as an administrative and commercial center for the surrounding coal- and forest-rich region.
  • 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_69ab4c3f2dcc819082df80f5e032f690 completed March 6, 2026, 9:50 p.m.
NER Named-entity recognition batch_69abd8fc8ee881908a9f6820d8934a62 completed March 7, 2026, 7:51 a.m.
NED1 Entity disambiguation (via context triple) batch_69af98bd689481908568d35baac1e065 completed March 10, 2026, 4:06 a.m.
Created at: March 6, 2026, 9:53 p.m.