Triple
T12789077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berar |
E305708
|
entity |
| Predicate | majorCity |
P316
|
FINISHED |
| Object | Akola |
E166095
|
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: Akola | Statement: [Berar, majorCity, Akola]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Akola Context triple: [Berar, majorCity, Akola]
-
A.
Akola
chosen
Akola is a major city in the Vidarbha region of Maharashtra, India, known as an important commercial and educational center.
-
B.
Alirajpur
Alirajpur is a town and district headquarters in western Madhya Pradesh, India, known for its predominantly tribal population and vibrant indigenous culture.
-
C.
Bhopalgarh
Bhopalgarh is a town in the Indian state of Rajasthan, known for its rural setting and administrative role within the region.
-
D.
Ashoknagar
Ashoknagar is a town and administrative district headquarters in the central Indian state of Madhya Pradesh, known for its agricultural economy and regional trade.
-
E.
Akola district
Akola district is an administrative district in the Vidarbha region of Maharashtra, India, known for its cotton-producing agriculture and the city of Akola as its headquarters.
- 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_69d7bdf366888190a8cccb982606889c |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96e6a61f48190972e241e70bc392c |
completed | April 10, 2026, 9:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6b8c75a048190aee92e50017c214e |
completed | May 3, 2026, 2:53 a.m. |
Created at: April 9, 2026, 5:30 p.m.