Triple
T15560490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Madhya Bharat |
E370983
|
entity |
| Predicate | includedRegion |
P285
|
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: [Madhya Bharat, includedRegion, Malwa]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Malwa Context triple: [Madhya Bharat, includedRegion, 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 (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_69d85cc6cf40819091f4a5facee1ebe6 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04ddb4c0c81909b3f4c75c91f7f3f |
completed | April 16, 2026, 2:47 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff456635588190a2473bcff3ae4a53 |
completed | May 9, 2026, 2:32 p.m. |
Created at: April 10, 2026, 4:09 a.m.