Triple
T13849517
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KRS Reservoir |
E332896
|
entity |
| Predicate | nearCity |
P350
|
FINISHED |
| Object | Srirangapatna |
E64345
|
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: Srirangapatna | Statement: [KRS Reservoir, nearCity, Srirangapatna]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Srirangapatna Context triple: [KRS Reservoir, nearCity, Srirangapatna]
-
A.
Srirangapatna
chosen
Srirangapatna is a historic island town in Karnataka, India, renowned as the former capital of Tipu Sultan and the Mysore Kingdom.
-
B.
Nayandahalli
Nayandahalli is a locality in southwestern Bangalore known as a key junction and residential area along major transport routes.
-
C.
Gorikot
Gorikot is a village and local hub in Pakistan’s Astore Valley, serving as a gateway to nearby mountain regions and trekking routes.
-
D.
Gudalur
Gudalur is a town in the Nilgiris region of Tamil Nadu, India, known for its tea plantations, forested hills, and proximity to wildlife sanctuaries.
-
E.
Sindhanur
Sindhanur is a town in Karnataka, India, known primarily for its extensive paddy cultivation and role as a major rice-producing 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_69d81c5ba13c8190839315f54768acfd |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de02d8fb788190baef7537be2baecb |
completed | April 14, 2026, 9:03 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fcb648146c8190842a3da4e4c0e217 |
completed | May 7, 2026, 3:56 p.m. |
Created at: April 9, 2026, 10:14 p.m.