Triple
T14051863
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mumbai Island |
E338110
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Bhuleshwar |
E919032
|
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: Bhuleshwar | Statement: [Mumbai Island, contains, Bhuleshwar]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bhuleshwar Context triple: [Mumbai Island, contains, Bhuleshwar]
-
A.
Bhuleshwar
chosen
Bhuleshwar is a densely populated, historic market and residential area in South Mumbai known for its traditional temples, jewelry and textile shops, and vibrant street life.
-
B.
Maheshwar
Maheshwar is a historic temple town on the banks of the Narmada River in Madhya Pradesh, India, renowned for its ghats, fort, and traditional handwoven Maheshwari sarees.
-
C.
Ramdurg
Ramdurg is a town in the Indian state of Karnataka, known for its historical temples and its location within the Belagavi region.
-
D.
Sangameshwar
Sangameshwar is a town in Maharashtra, India, historically notable as the site where Maratha ruler Sambhaji was captured by Mughal forces.
-
E.
Tuljapur
Tuljapur is a town in Maharashtra, India, renowned as a major pilgrimage center for the goddess Bhavani.
- 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_69d81c664e48819088cbd8f433aeffe5 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de3c8a518081908ad030ba48b7b946 |
completed | April 14, 2026, 1:09 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fcb65e63b48190bd5bd4a36cd15396 |
completed | May 7, 2026, 3:57 p.m. |
Created at: April 9, 2026, 10:20 p.m.