Triple
T16592639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Koyna River |
E403127
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Koynanagar |
E879484
|
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: Koynanagar | Statement: [Koyna River, near, Koynanagar]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Koynanagar Context triple: [Koyna River, near, Koynanagar]
-
A.
Koynanagar
chosen
Koynanagar is a small town in Maharashtra, India, known primarily for its proximity to the major hydroelectric Koyna Dam in the Western Ghats.
-
B.
Walajapet
Walajapet is a historic town in the Indian state of Tamil Nadu, known as an early center of trade and administration in the region.
-
C.
Karanpur
Karanpur is a town located in the Ganganagar district of the northern Indian state of Rajasthan.
-
D.
Tatanagar
Tatanagar is an industrial city in the Indian state of Jharkhand, best known as Jamshedpur, the steel-producing company town founded by the Tata Group.
-
E.
Taranagar
Taranagar is a town in the Churu district of Rajasthan, India, known for its regional trade, educational institutions, 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_69d88387363c8190a97a0c942130de97 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e359a123e8819095cd73cd848a3345 |
completed | April 18, 2026, 10:14 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00759dea5c819083fe9fb7dee37a35 |
completed | May 10, 2026, 12:10 p.m. |
Created at: April 10, 2026, 5:16 a.m.