Triple
T8629134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ghataprabha Dam |
E204355
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Gokak |
E744799
|
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: Gokak | Statement: [Ghataprabha Dam, locatedNear, Gokak]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gokak Context triple: [Ghataprabha Dam, locatedNear, Gokak]
-
A.
Gokak
chosen
Gokak is a town in the Indian state of Karnataka known for its historic textile industry and the scenic Gokak Falls on the Ghataprabha River.
-
B.
Sangole
Sangole is a town in Maharashtra, India, known for its agricultural markets and location within Solapur district.
-
C.
Sakesar
Sakesar is a prominent mountain peak in Pakistan’s Punjab region, known for its scenic views, cooler climate, and strategic location within the Salt Range.
-
D.
Goghat
Goghat is a town in West Bengal, India, known primarily as a rural administrative and agricultural center within the Hooghly region.
-
E.
Bhailsa
Bhailsa is the former historical name of Vidisha, an ancient city in the central Indian state of Madhya Pradesh known for its rich archaeological and cultural heritage.
- 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_69ca834a4ea0819094970dceb9e389f3 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc473f6b888190ae40d65f24122c88 |
completed | March 31, 2026, 10:14 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cecca2a3e48190b74ed3c948196409 |
completed | April 2, 2026, 8:08 p.m. |
Created at: March 30, 2026, 6:27 p.m.