Triple
T14225021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Navi Mumbai |
E352594
|
entity |
| Predicate | hasResidentialZone |
P9064
|
FINISHED |
| Object | Panvel |
E288896
|
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: Panvel | Statement: [Navi Mumbai, hasResidentialZone, Panvel]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Panvel Context triple: [Navi Mumbai, hasResidentialZone, Panvel]
-
A.
Panvel
chosen
Panvel is a major railway and commercial hub in Navi Mumbai, Maharashtra, serving as an important junction and gateway between Mumbai and the wider Konkan region.
-
B.
Belapur
Belapur is a major suburban node in Navi Mumbai, India, known for its commercial centers, residential areas, and role as a key transport hub.
-
C.
Thane
Thane is a major city in western India known for its numerous lakes and its proximity to Mumbai.
-
D.
Navi Mumbai
Navi Mumbai is a planned satellite city across the harbor from Mumbai, developed to decongest the main metropolis and featuring organized residential, commercial, and industrial zones.
-
E.
Vikhroli
Vikhroli is a suburban neighborhood in Mumbai known for its residential areas, industrial estates, and proximity to major transport links.
- 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_69d8278a06e481908b5d6af0a8afe737 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de6228e53c8190abbe4e2d88a7362a |
completed | April 14, 2026, 3:50 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd3d0e6abc819097c0c9bdc08387f6 |
completed | May 8, 2026, 1:31 a.m. |
Created at: April 10, 2026, 1:06 a.m.