Triple
T23395341
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berar region |
E559341
|
entity |
| Predicate | majorCity |
P316
|
FINISHED |
| Object | Yavatmal |
—
|
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: Yavatmal | Statement: [Berar region, majorCity, Yavatmal]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yavatmal Context triple: [Berar region, majorCity, Yavatmal]
-
A.
Yavatmal
chosen
Yavatmal is a city in the Indian state of Maharashtra, known as a regional center in the Vidarbha area with a predominantly agrarian economy.
-
B.
Bantva
Bantva is a town in the Indian state of Gujarat, historically known as a trading center and as the birthplace of renowned humanitarian Abdul Sattar Edhi.
-
C.
Banavasi
Banavasi is an ancient town in Karnataka, India, historically significant as an early capital of the Kadamba dynasty and a major center of early Kannada culture and inscriptions.
-
D.
Vyadhapura
Vyadhapura was the principal urban and political center of the ancient Southeast Asian kingdom of Funan, located in the lower Mekong region.
-
E.
Jwalapur
Jwalapur is a prominent suburban town and commercial hub near Haridwar in the Indian state of Uttarakhand.
- 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_69e24549610c8190a069d6411ce5f661 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1a4db1c888190ace5d58bcc8645c1 |
completed | April 29, 2026, 6:27 a.m. |
Created at: April 17, 2026, 5:36 p.m.