Triple
T16381956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mumbai–Pune Expressway |
E397826
|
entity |
| Predicate | passesNear |
P416
|
FINISHED |
| Object | Khandala |
E92515
|
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: Khandala | Statement: [Mumbai–Pune Expressway, passesNear, Khandala]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Khandala Context triple: [Mumbai–Pune Expressway, passesNear, Khandala]
-
A.
Khandala
chosen
Khandala is a popular hill station in Maharashtra, India, known for its scenic valleys, waterfalls, and trekking spots in the Western Ghats.
-
B.
Chiplun
Chiplun is a town in Maharashtra, India, situated along the Vashishti River and known as a commercial and transport hub in the Konkan region.
-
C.
Ghansoli
Ghansoli is a rapidly developing residential and commercial node in Navi Mumbai, Maharashtra, known for its growing IT parks, educational institutions, and connectivity to Mumbai via rail and road.
-
D.
Kundalpur
Kundalpur is a historically significant Jain pilgrimage site in India, revered as the birthplace of Lord Mahavira.
-
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_69d87f2880b48190ae1a9673a3bbef80 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e319dd0e0c8190812bde6a2f7d9644 |
completed | April 18, 2026, 5:42 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00758847948190b616cc85e208ee61 |
completed | May 10, 2026, 12:09 p.m. |
Created at: April 10, 2026, 5:08 a.m.