Triple
T11813890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bhandup |
E280946
|
entity |
| Predicate | hasSubLocality |
P747
|
FINISHED |
| Object | Bhandup East |
E280946
|
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: Bhandup East | Statement: [Bhandup, hasSubLocality, Bhandup East]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bhandup East Context triple: [Bhandup, hasSubLocality, Bhandup East]
-
A.
Bhandup
chosen
Bhandup is a suburban residential and industrial locality in the northeastern part of Mumbai, India.
-
B.
Bhayandar East
Bhayandar East is a suburban locality in the Mira-Bhayandar region of Maharashtra, India, known for its residential neighborhoods and growing urban infrastructure.
-
C.
Bhayandar West
Bhayandar West is a suburban locality in the Mira-Bhayandar region of Maharashtra, India, known for its residential neighborhoods and growing commercial activity.
-
D.
Ghatkopar
Ghatkopar is a densely populated residential and commercial suburb in eastern Mumbai, known for its bustling markets, connectivity, and vibrant Gujarati community.
-
E.
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.
- 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_69d6ab26aae88190b2489efcb2a24234 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a5cba708819097467bb7aca7fc65 |
completed | April 10, 2026, 7:24 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f78ac420788190b12167aef7436c64 |
completed | May 3, 2026, 5:49 p.m. |
Created at: April 8, 2026, 9:42 p.m.