Triple
T16685788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pimpri-Chinchwad |
E405457
|
entity |
| Predicate | hasSuburb |
P747
|
FINISHED |
| Object | Bhosari |
E1223192
|
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: Bhosari | Statement: [Pimpri-Chinchwad, hasSuburb, Bhosari]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bhosari Context triple: [Pimpri-Chinchwad, hasSuburb, Bhosari]
-
A.
Bhosari
chosen
Bhosari is a prominent industrial suburb in the Pune Metropolitan Region known for its manufacturing hubs and industrial estates.
-
B.
Chembur
Chembur is a prominent suburban neighborhood in eastern Mumbai known for its residential areas, connectivity, and growing commercial and industrial presence.
-
C.
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.
-
D.
Dhanyawadi
Dhanyawadi was an ancient city that served as one of the earliest and most important royal centers of the Arakan (Rakhine) region in present-day western Myanmar.
-
E.
Vaibhavwadi
Vaibhavwadi is a small town in Maharashtra’s Sindhudurg district, known for its scenic Konkan landscape and proximity to Kankavli.
- 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_69d8838c28748190b3f5967c743940ab |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37ea550c0819085bd36c44237a61a |
completed | April 18, 2026, 12:52 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a009d32e7b48190b7dd4660bed4789d |
completed | May 10, 2026, 2:58 p.m. |
Created at: April 10, 2026, 5:19 a.m.