Triple

T5698981
Position Surface form Disambiguated ID Type / Status
Subject Badakhshan E125610 entity
Predicate crossedBy P416 FINISHED
Object Kokcha River E444420 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: Kokcha River | Statement: [Badakhshan, crossedBy, Kokcha River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kokcha River
Context triple: [Badakhshan, crossedBy, Kokcha River]
  • A. Kokcha River chosen
    The Kokcha River is a significant tributary of the Amu Darya in northeastern Afghanistan, flowing through Badakhshan and past the ancient Greco-Bactrian city of Ai-Khanoum.
  • B. Aksu River
    The Aksu River is a major river in northwestern China and Kyrgyzstan that forms the principal headwater of the Tarim River in the arid Tarim Basin.
  • 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. Hotan River
    The Hotan River is a major river in China’s Xinjiang region that flows northward across the Taklamakan Desert to help form the Tarim River.
  • E. Asan River
    The Asan River is a Himalayan foothill river in northern India that joins the Tons River and is known for the Asan Barrage and its surrounding bird sanctuary.
  • 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_69c0082c96988190b3a6a201edce472a completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c0240ecef48190bdef10b38ecb2bd0 completed March 22, 2026, 5:17 p.m.
NED1 Entity disambiguation (via context triple) batch_69c11ca111188190932a17a2fab097c7 completed March 23, 2026, 10:57 a.m.
Created at: March 22, 2026, 3:45 p.m.