Triple
T14517611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BLR |
E340563
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Devanahalli |
E340565
|
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: Devanahalli | Statement: [BLR, locatedNear, Devanahalli]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Devanahalli Context triple: [BLR, locatedNear, Devanahalli]
-
A.
Devanahalli
chosen
Devanahalli is a town near Bengaluru in the Indian state of Karnataka, notable for its rapid development and proximity to Kempegowda International Airport.
-
B.
Nayandahalli
Nayandahalli is a locality in southwestern Bangalore known as a key junction and residential area along major transport routes.
-
C.
Bhadravan
Bhadravan is one of the twelve sacred forests of Vraja associated with the pastimes of Lord Krishna in Hindu tradition.
-
D.
Thippagondanahalli
Thippagondanahalli is a village in Karnataka, India, best known for the nearby Thippagondanahalli Dam that serves as a major water source for Bengaluru.
-
E.
Mahadevapura
Mahadevapura is a rapidly developing residential and commercial neighborhood in eastern Bengaluru, India, known for its proximity to major IT parks and tech hubs.
- 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_69d822d9c0408190b9a2b3643e58bb4d |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69de9a6f50208190b687b505f5cd1aa2 |
completed | April 14, 2026, 7:50 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd6da80dc88190afa96760efb0c7de |
completed | May 8, 2026, 4:59 a.m. |
Created at: April 10, 2026, 1:22 a.m.