Triple
T11925644
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dadar |
E283774
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Mahim |
E647085
|
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: Mahim | Statement: [Dadar, near, Mahim]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mahim Context triple: [Dadar, near, Mahim]
-
A.
Mahim
chosen
Mahim is a historic coastal neighborhood in Mumbai, India, known for its centuries-old fort, prominent religious sites, and role as one of the original seven islands that formed the city.
-
B.
Ghamra
Ghamra is a station on Cairo's Metro network, located along the system's first and oldest line.
-
C.
Yaudheya
Yaudheya is a relatively lesser-known figure in the Mahabharata tradition, remembered primarily as a son of the Pandava king Yudhishthira.
-
D.
Kala Pani
Kala Pani is the infamous British-era colonial prison in the Andaman and Nicobar Islands, known for its harsh conditions and use to exile Indian freedom fighters.
-
E.
Mahoba
Mahoba is a historic town in Uttar Pradesh, India, renowned for its role as a prominent center of power and culture in the Bundelkhand region, especially under the Chandela rulers.
- 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_69d6ab2ce9c48190b5d39511b524f666 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8e8e3ff308190851ce656286bc67e |
completed | April 10, 2026, 12:11 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f440525e9881909b21df139d97d986 |
completed | May 1, 2026, 5:55 a.m. |
Created at: April 8, 2026, 9:45 p.m.