Triple

T6734770
Position Surface form Disambiguated ID Type / Status
Subject Dhar E153725 entity
Predicate locatedInRegion P40 FINISHED
Object Malwa E60527 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: Malwa | Statement: [Dhar, locatedInRegion, Malwa]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Malwa
Context triple: [Dhar, 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. Chalsa
    Chalsa is a small town in West Bengal, India, known as a gateway to the Dooars region’s tea gardens and wildlife reserves.
  • C. Churulia
    Churulia is a village in the Paschim Bardhaman district of West Bengal, India, best known as the birthplace of the revolutionary poet Kazi Nazrul Islam.
  • D. Salbai
    Salbai is a historical location in India known primarily as the site where the 1782 Treaty of Salbai was concluded between the British East India Company and the Maratha Empire.
  • E. Maddur
    Maddur is a town in Karnataka, India, known for its location between Bengaluru and Mysuru and its popular local snack, Maddur vada.
  • 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_69c6880bdd68819097de8b6099992682 completed March 27, 2026, 1:37 p.m.
NER Named-entity recognition batch_69c6d16ecbe08190b019d547f631a725 completed March 27, 2026, 6:50 p.m.
NED1 Entity disambiguation (via context triple) batch_69c70b0703288190906cfcaba9d9c85a completed March 27, 2026, 10:56 p.m.
Created at: March 27, 2026, 2:09 p.m.