Triple
T17072702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ahmednagar district |
E414261
|
entity |
| Predicate | hasMajorTown |
P316
|
FINISHED |
| Object | Kopargaon |
E551342
|
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: Kopargaon | Statement: [Ahmednagar district, hasMajorTown, Kopargaon]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kopargaon Context triple: [Ahmednagar district, hasMajorTown, Kopargaon]
-
A.
Kopargaon
chosen
Kopargaon is a town in the Ahmednagar district of Maharashtra, India, known as a commercial and transport hub near the pilgrimage city of Shirdi.
-
B.
Dharbandora
Dharbandora is a taluka (administrative subdivision) in the Indian state of Goa, located within the South Goa district.
-
C.
Khanapur
Khanapur is a town in the Indian state of Karnataka known for its scenic surroundings, forested areas, and proximity to the Western Ghats.
-
D.
Talegaon
Talegaon is an industrial town in the Pune Metropolitan Region of Maharashtra, India, known for its manufacturing hubs and proximity to Pune city.
-
E.
Dhrol
Dhrol is a town in the Jamnagar district of Gujarat, India, known historically as the seat of the former princely Dhrol State.
- 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_69d886cef44c8190ba56c44b4e863e64 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dbc28fec81909c39d432094d9cdd |
completed | April 18, 2026, 7:30 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a012edbce988190a784448ba8a258a5 |
completed | May 11, 2026, 1:20 a.m. |
Created at: April 10, 2026, 5:34 a.m.