Triple

T12606642
Position Surface form Disambiguated ID Type / Status
Subject Topi E300995 entity
Predicate near P350 FINISHED
Object Tarbela Dam E76597 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: Tarbela Dam | Statement: [Topi, near, Tarbela Dam]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tarbela Dam
Context triple: [Topi, near, Tarbela Dam]
  • A. Tarbela Dam chosen
    Tarbela Dam is one of the world’s largest earth-filled dams, located in Pakistan and serving as a major source of hydroelectric power and irrigation water.
  • B. Taunsa Barrage
    Taunsa Barrage is a major irrigation and flood-control structure on the Indus River in Punjab, Pakistan, crucial for regional agriculture and water management.
  • C. Tajewala Barrage
    Tajewala Barrage was an older irrigation and water diversion structure on the Yamuna River in Haryana, India, that was eventually superseded by the modern Hathni Kund Barrage.
  • D. Karun-1 Dam
    Karun-1 Dam is a major hydroelectric arch dam in southwestern Iran, built on the Karun River to generate power and control floods.
  • E. Temghar Dam
    Temghar Dam is a major earthfill dam in Maharashtra, India, built for water supply, irrigation, and flood control in the Pune 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_69d7bdea2ca881908f379526c13b1145 completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d954e7f2dc8190a42cab7a0e5ea7f3 completed April 10, 2026, 7:52 p.m.
NED1 Entity disambiguation (via context triple) batch_69f65ecd1b748190bd961497b30e1ae5 completed May 2, 2026, 8:30 p.m.
Created at: April 9, 2026, 5:11 p.m.