Triple

T19573854
Position Surface form Disambiguated ID Type / Status
Subject Qarshi E489795 entity
Predicate locatedOnRiver P165 FINISHED
Object Kashkadarya River NE NERFINISHED

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: Kashkadarya River | Statement: [Qarshi, locatedOnRiver, Kashkadarya River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kashkadarya River
Context triple: [Qarshi, locatedOnRiver, Kashkadarya River]
  • A. Kashkadarya River chosen
    The Kashkadarya River is a river in southern Uzbekistan that flows through the city of Karshi and irrigates the surrounding arid agricultural region.
  • B. Kara Darya
    Kara Darya is a major river in Central Asia that flows through Kyrgyzstan and Uzbekistan, helping to form the Syr Darya and irrigate the fertile Ferghana Valley.
  • C. Andijan-Say River
    The Andijan-Say River is a watercourse in eastern Uzbekistan that flows through the city of Andijan in the fertile Fergana Valley.
  • D. Kyzyl-Suu River
    The Kyzyl-Suu River is a Central Asian mountain river that serves as one of the principal headwaters of the Vakhsh River.
  • E. Khash River
    The Khash River is a tributary watercourse in southwestern Afghanistan that feeds into the larger Helmand River system.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8e8dd9374819098e36349b3211663 completed April 10, 2026, 12:11 p.m.
NER Named-entity recognition batch_69e6402333dc8190bdffb1da68e2c76b completed April 20, 2026, 3:02 p.m.
Created at: April 10, 2026, 1:42 p.m.