Triple
T14051859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mumbai Island |
E338110
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Girgaon |
E995167
|
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: Girgaon | Statement: [Mumbai Island, contains, Girgaon]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Girgaon Context triple: [Mumbai Island, contains, Girgaon]
-
A.
Girgaon
chosen
Girgaon is a historic, densely populated neighborhood in South Mumbai known for its traditional Marathi culture, old chawls, and proximity to Girgaum Chowpatty beach.
-
B.
Ghojadanga
Ghojadanga is a border checkpoint locality in West Bengal, India, situated near the India–Bangladesh frontier in North 24 Parganas district.
-
C.
Dharangaon
Dharangaon is a town in the Jalgaon district of Maharashtra, India, known for its agricultural surroundings and role as a local commercial center.
-
D.
Dergaon
Dergaon is a prominent town in Assam, India, known for its historical significance and role as an important local center within the Golaghat district.
-
E.
Satgaon
Satgaon was a historically significant port city in the Bengal region, flourishing as a major center of trade and commerce under the Bengal Sultanate.
- 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_69fbc346ff2c81909dfc29ef6624181f |
completed | May 6, 2026, 10:40 p.m. |
Created at: April 9, 2026, 10:20 p.m.