Triple
T16275819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khandala railway station |
E395123
|
entity |
| Predicate | serves |
P98
|
FINISHED |
| Object | Khandala town |
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 town | Statement: [Khandala railway station, serves, Khandala town]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Khandala town Context triple: [Khandala railway station, serves, Khandala town]
-
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.
Chandwad
Chandwad is a town in the Nashik district of Maharashtra, India, known for its historical temples and hill forts.
-
C.
Kundalpur
Kundalpur is a historically significant Jain pilgrimage site in India, revered as the birthplace of Lord Mahavira.
-
D.
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.
-
E.
Sohna town
Sohna town is a rapidly developing suburban area in Haryana, India, known for its hot springs, proximity to the Aravalli hills, and growing residential and commercial hubs.
- 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_69d87f221d8081909b0b2063e7528ba2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2460d30608190a721aa845fcf7cf6 |
completed | April 17, 2026, 2:39 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a001f90d4088190915d701978f018a5 |
completed | May 10, 2026, 6:02 a.m. |
Created at: April 10, 2026, 5:05 a.m.