Triple
T13037780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ghatkopar |
E326607
|
entity |
| Predicate | connectedTo |
P37
|
FINISHED |
| Object | Kurla |
E274832
|
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: Kurla | Statement: [Ghatkopar, connectedTo, Kurla]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kurla Context triple: [Ghatkopar, connectedTo, Kurla]
-
A.
Kurla
chosen
Kurla is a densely populated suburban neighborhood in Mumbai, India, known as a major residential, commercial, and transport hub of the city.
-
B.
Dadar
Dadar is a major commercial and residential neighborhood in central Mumbai, India, known as a key transit hub and marketplace in the city.
-
C.
Thane
Thane is a major city in western India known for its numerous lakes and its proximity to Mumbai.
-
D.
Mumbra
Mumbra is a densely populated suburban area in the Thane district of Maharashtra, India, known for its largely Muslim population and rapid urban growth.
-
E.
Kopar Khairane
Kopar Khairane is a rapidly developing residential and commercial node in Navi Mumbai, Maharashtra, known for its growing infrastructure and connectivity to Mumbai and Thane.
- 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_69d8076cc45c81908123123f43e69266 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d9804b743c8190810dc5c14bc6d912 |
completed | April 10, 2026, 10:57 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6ead25b7c8190af2ccf26b44c2ea2 |
completed | May 3, 2026, 6:27 a.m. |
Created at: April 9, 2026, 8:55 p.m.