Triple
T16528561
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hinjawadi |
E401501
|
entity |
| Predicate | nearTo |
P350
|
FINISHED |
| Object | Aundh |
E440516
|
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: Aundh | Statement: [Hinjawadi, nearTo, Aundh]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Aundh Context triple: [Hinjawadi, nearTo, Aundh]
-
A.
Aundh
chosen
Aundh is a locality in Pune, Maharashtra, India, known for its residential neighborhoods, shopping areas, and proximity to major city hubs.
-
B.
Tanguturi
Tanguturi is the given name of T. Prakasam, a prominent Indian freedom fighter and former Chief Minister of the Madras Presidency and Andhra State.
-
C.
Assandh
Assandh is a town in the Karnal district of Haryana, India, known for its agricultural economy and proximity to major regional transport routes.
-
D.
Yaganti
Yaganti is a historic temple town in Andhra Pradesh, India, renowned for its ancient Sri Yagantiswamy (Shiva) temple and distinctive rock formations.
-
E.
Budhlada
Budhlada is a town in the Mansa district of Punjab, India, known as a regional commercial and agricultural center.
- 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_69d883838abc8190bc79cb2d41733ce2 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32ed57be481908625d4c5aab0940c |
completed | April 18, 2026, 7:12 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00608efd0c81908e64419bd74eb285 |
completed | May 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 5:14 a.m.