Triple

T3531021
Position Surface form Disambiguated ID Type / Status
Subject Kota E74659 entity
Predicate locatedIn P40 FINISHED
Object Hadoti E74659 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: Hadoti | Statement: [Kota, locatedIn, Hadoti]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hadoti
Context triple: [Kota, locatedIn, Hadoti]
  • A. Hadoti chosen
    Hadoti is a cultural and geographic region in southeastern Rajasthan, India, known for its historic cities like Kota and Bundi and its distinctive Hadoti dialect of Rajasthani.
  • B. Charotar
    Charotar is a fertile, culturally distinct region of central Gujarat in western India, known for its agrarian prosperity and significant diaspora.
  • C. Bundelkhand
    Bundelkhand is a historic and culturally distinct region in central India, spanning parts of present-day Uttar Pradesh and Madhya Pradesh, known for its rugged terrain, forts, and rich medieval heritage.
  • D. Shekhawati
    Shekhawati is a dialect of the Rajasthani language spoken primarily in the Shekhawati region of northern Rajasthan, India.
  • E. Kutch
    Kutch is a large district in western India known for its salt desert landscapes, rich handicraft traditions, and vibrant cultural festivals.
  • 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_69ad85d1a3948190931fd1ea1f49717b completed March 8, 2026, 2:21 p.m.
NER Named-entity recognition batch_69adbc988ee081909c6b9d5eed0d2d6d completed March 8, 2026, 6:14 p.m.
NED1 Entity disambiguation (via context triple) batch_69b48823ca248190a34d2d0eb3a496a7 completed March 13, 2026, 9:56 p.m.
Created at: March 8, 2026, 3:19 p.m.