Triple

T30510622
Position Surface form Disambiguated ID Type / Status
Subject Tarko-Sale E776407 entity
Predicate locatedOnRiver P165 FINISHED
Object Pyakupur River
The Pyakupur River is a waterway in the Yamalo-Nenets Autonomous Okrug of Russia that flows through the town of Tarko-Sale and forms part of the region’s extensive Siberian river system.
E2037973 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: Pyakupur River | Statement: [Tarko-Sale, locatedOnRiver, Pyakupur 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: Pyakupur River
Triple: [Tarko-Sale, locatedOnRiver, Pyakupur River]
Generated description
The Pyakupur River is a waterway in the Yamalo-Nenets Autonomous Okrug of Russia that flows through the town of Tarko-Sale and forms part of the region’s extensive Siberian river system.

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_69f2249a155c8190b1d512106007e9bb completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69f687b8c6448190a0f724dbaefcf023 completed May 2, 2026, 11:24 p.m.
NED1 Entity disambiguation (via context triple) batch_6a3515f164888190aa2c50722bcc3fcd completed June 19, 2026, 10:12 a.m.
NEDg Description generation batch_6a35169eea84819084fa7afcab1bc6a2 completed June 19, 2026, 10:14 a.m.
NED2 Entity disambiguation (via description) batch_6a35171ad54881908aefba332ec1eb78 completed June 19, 2026, 10:16 a.m.
Created at: April 29, 2026, 8:16 p.m.