Triple
T7922595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atmakur |
E183981
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Jurala Dam |
E34752
|
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: Jurala Dam | Statement: [Atmakur, near, Jurala Dam]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Jurala Dam Context triple: [Atmakur, near, Jurala Dam]
-
A.
Jurala Dam
chosen
Jurala Dam is a major irrigation and hydroelectric project built across the Krishna River in Telangana, India.
-
B.
Baipaza Dam
Baipaza Dam is a major hydroelectric dam in Tajikistan that harnesses the Vakhsh River to generate power and support regional water management.
-
C.
Kremasta Dam
Kremasta Dam is a major hydroelectric and water management dam in western Greece, forming one of the country’s largest artificial lakes.
-
D.
Edea Dam
Edea Dam is a major hydroelectric power facility in Cameroon that harnesses the flow of the Sanaga River to generate electricity.
-
E.
Zhinvali Dam
Zhinvali Dam is a large hydroelectric dam and reservoir in eastern Georgia, known for its striking turquoise waters and role in supplying water and power to the region.
- 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_69ca828fe7bc819090f52c88dcd72183 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3aaadd1c8190971f2a6c7636cae4 |
completed | March 31, 2026, 3:08 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ccbde69b608190a49d93c04c46787d |
completed | April 1, 2026, 6:40 a.m. |
Created at: March 30, 2026, 5:06 p.m.