Triple

T20638030
Position Surface form Disambiguated ID Type / Status
Subject Ujjain district E507137 entity
Predicate locatedInRegion P40 FINISHED
Object Malwa 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: Malwa | Statement: [Ujjain district, locatedInRegion, Malwa]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Malwa
Context triple: [Ujjain district, locatedInRegion, Malwa]
  • A. Malwa chosen
    Malwa is a historical region in central India, known for its fertile plateau, strategic location, and significant role in medieval and early modern Indian politics and culture.
  • B. Balwa
    Balwa is a municipality-level city located in Nepal's Madhesh Province.
  • C. Makasara
    Makasara is the native name (endonym) for the Makassarese language spoken by the Makassarese people of South Sulawesi, Indonesia.
  • D. Malwa region
    The Malwa region is a historical and cultural area in the southern part of Punjab, India, known for its distinct Punjabi dialect, agrarian economy, and rich folk traditions.
  • E. Chalsa
    Chalsa is a small town in West Bengal, India, known as a gateway to the Dooars region’s tea gardens and wildlife reserves.
  • 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_69e0b4be702c8190a3d2410a881d310a completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e6ad1163008190aa9df36750a952d2 completed April 20, 2026, 10:47 p.m.
Created at: April 16, 2026, 11:42 a.m.