Triple
T14896458
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | INS Shivaji |
E359888
|
entity |
| Predicate | location |
P40
|
FINISHED |
| Object | Lonavala |
E91226
|
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: Lonavala | Statement: [INS Shivaji, location, Lonavala]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lonavala Context triple: [INS Shivaji, location, Lonavala]
-
A.
Lonavala
chosen
Lonavala is a popular hill station in Maharashtra, India, known for its lush green valleys, waterfalls, and scenic views along the Mumbai–Pune route.
-
B.
Lohegaon
Lohegaon is a suburban area of Pune, India, known for its residential neighborhoods and proximity to key transport and defense installations.
-
C.
Amboli hill station
Amboli hill station is a scenic, high-altitude resort town in Maharashtra’s Sahyadri range, known for its cool climate, dense forests, and numerous waterfalls.
-
D.
Khandala
Khandala is a popular hill station in Maharashtra, India, known for its scenic valleys, waterfalls, and trekking spots in the Western Ghats.
-
E.
Mavli
Mavli is a town in Rajasthan, India, known as a local transport and railway junction within the Udaipur district.
- 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_69d827980cbc8190a0c569ae3940a1d9 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69ded6070b248190be8f4f91a0c0b1f3 |
completed | April 15, 2026, 12:04 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe6b679fb081908cf8f41acfba3b99 |
completed | May 8, 2026, 11:01 p.m. |
Created at: April 10, 2026, 2:11 a.m.