Triple
T17127492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viman Nagar |
E415634
|
entity |
| Predicate | proximityTo |
P350
|
FINISHED |
| Object | Yerawada |
E94732
|
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: Yerawada | Statement: [Viman Nagar, proximityTo, Yerawada]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yerawada Context triple: [Viman Nagar, proximityTo, Yerawada]
-
A.
Yerawada
chosen
Yerawada is a prominent neighborhood in Pune, India, known for its major prison, dense residential areas, and growing commercial and IT-related developments.
-
B.
Uraku
Uraku is a Japanese surname associated with individuals such as Akinobu Uraku.
-
C.
Gotemba
Gotemba is a Japanese city in Shizuoka Prefecture known as a gateway to Mount Fuji and a popular base for outdoor activities and outlet shopping.
-
D.
Yamadera
Yamadera is a historic mountainside temple complex in Japan’s Tohoku region, famed for its scenic cliffside halls and panoramic valley views.
-
E.
Sendagaya
Sendagaya is a neighborhood in Tokyo known for its sports facilities, including the National Stadium, and its proximity to Shinjuku and Harajuku.
- 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_69d886d090cc8190a39cb94992586905 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3f027a3d081908fc1134b50db3d45 |
completed | April 18, 2026, 8:57 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a013a145e7481909242aab69baeb7a0 |
completed | May 11, 2026, 2:08 a.m. |
Created at: April 10, 2026, 5:36 a.m.