Triple
T11443922
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mankhurd |
E271214
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Vashi |
E268120
|
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: Vashi | Statement: [Mankhurd, locatedNear, Vashi]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Vashi Context triple: [Mankhurd, locatedNear, Vashi]
-
A.
Vashi
chosen
Vashi is a major suburban railway station and commercial-residential hub in Navi Mumbai, India.
-
B.
Modasa
Modasa is a town in the Indian state of Gujarat that serves as the administrative headquarters of Aravalli district.
-
C.
Kharadi
Kharadi is a rapidly developing suburb in Pune, India, known as a major IT and business hub with modern infrastructure and residential complexes.
-
D.
Barvikha
Barvikha is an affluent suburban settlement west of Moscow, known for its luxury residences, elite dachas, and high-profile residents from Russia’s political and business elite.
-
E.
Shamshabad
Shamshabad is a suburban area near Hyderabad in the Indian state of Telangana, known primarily for hosting the Rajiv Gandhi International Airport.
- 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_69d6aadff8888190a13f253f0d460874 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8088a66f48190b2b4a56cd62097cf |
completed | April 9, 2026, 8:14 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e5e8f8049881909c1a52101e4620b3 |
completed | April 20, 2026, 8:51 a.m. |
Created at: April 8, 2026, 9:35 p.m.