Triple
T10070107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bhavra |
E213598
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Alirajpur town |
E148030
|
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: Alirajpur town | Statement: [Bhavra, locatedNear, Alirajpur town]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Alirajpur town Context triple: [Bhavra, locatedNear, Alirajpur town]
-
A.
Alirajpur
chosen
Alirajpur is a town and district headquarters in western Madhya Pradesh, India, known for its predominantly tribal population and vibrant indigenous culture.
-
B.
Rajpura
Rajpura is an industrial and commercial town in the Patiala district of Punjab, India, known for its manufacturing base and strategic location as a transport hub.
-
C.
Hoshangabad
Hoshangabad is a city in the Indian state of Madhya Pradesh, known for its location on the banks of the Narmada River and its agricultural and industrial activities.
-
D.
Ballarpur
Ballarpur is an industrial town in Maharashtra, India, known particularly for its large paper manufacturing industry.
-
E.
Bhopalgarh
Bhopalgarh is a town in the Indian state of Rajasthan, known for its rural setting and administrative role within the 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_69ca839add308190b57d53b4ec21f2d0 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cdcffa045c8190a08db0bb74cb006a |
completed | April 2, 2026, 2:10 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d29aa05cc881909f59178e9c6c01ef |
completed | April 5, 2026, 5:23 p.m. |
Created at: March 30, 2026, 8:58 p.m.