Triple

T31908471
Position Surface form Disambiguated ID Type / Status
Subject Kondoma River basin E814617 entity
Predicate drainedBy P165 FINISHED
Object Kondoma River
The Kondoma River is a waterway in southwestern Siberia, Russia, that flows through the Kemerovo Oblast and serves as a tributary of the Tom River within the Ob River basin.
E2296949 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: Kondoma River | Statement: [Kondoma River basin, drainedBy, Kondoma 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: Kondoma River
Triple: [Kondoma River basin, drainedBy, Kondoma River]
Generated description
The Kondoma River is a waterway in southwestern Siberia, Russia, that flows through the Kemerovo Oblast and serves as a tributary of the Tom River within the Ob River basin.

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_69f348f109d88190b5005372c53d2fcd completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f6b1b6a1f08190b1d5306ae35977cb completed May 3, 2026, 2:23 a.m.
NED1 Entity disambiguation (via context triple) batch_6a82e255d2ac8190876d840aa1ae74f5 completed Aug. 17, 2026, 10:28 a.m.
NEDg Description generation batch_6a82e2b8e76081909f0e207fd2276bc7 completed Aug. 17, 2026, 10:30 a.m.
NED2 Entity disambiguation (via description) batch_6a82e5918d2c81909b386bdca6c8b3ec completed Aug. 17, 2026, 10:42 a.m.
Created at: May 1, 2026, 12:01 a.m.