Triple

T34283261
Position Surface form Disambiguated ID Type / Status
Subject Shaksgam River E879654 entity
Predicate hasAlternativeName P39 FINISHED
Object Kelechin River
The Kelechin River, also known as the Shaksgam River, is a remote high-altitude river flowing through the disputed Shaksgam Valley region north of the Karakoram Range.
E2285711 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: Kelechin River | Statement: [Shaksgam River, hasAlternativeName, Kelechin River]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Kelechin River
Triple: [Shaksgam River, hasAlternativeName, Kelechin River]
Generated description
The Kelechin River, also known as the Shaksgam River, is a remote high-altitude river flowing through the disputed Shaksgam Valley region north of the Karakoram Range.

Provenance (5 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_69f349b5f6648190b9420d94a4cd16e0 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f712f1812881909bcfc89c02c4514a completed May 3, 2026, 9:18 a.m.
NED1 Entity disambiguation (via context triple) batch_6a460e5281c081909cda32b43c8f9b6d completed July 2, 2026, 7:08 a.m.
NEDg Description generation batch_6a461226718881908f3a3a2b036dac38 completed July 2, 2026, 7:24 a.m.
NED2 Entity disambiguation (via description) batch_6a4612a8097c8190ac6a31ed5d69df44 completed July 2, 2026, 7:26 a.m.
Created at: May 1, 2026, 1:57 a.m.