Triple

T22847297
Position Surface form Disambiguated ID Type / Status
Subject Central Mongolia E566257 entity
Predicate hasMajorRiver P165 FINISHED
Object Selenge 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: Selenge River | Statement: [Central Mongolia, hasMajorRiver, Selenge River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Selenge River
Context triple: [Central Mongolia, hasMajorRiver, Selenge River]
  • A. Selenge River chosen
    The Selenge River is a major river in Mongolia and Russia that drains into Lake Baikal and forms the largest inflow to the lake’s watershed.
  • B. Bulgan River
    The Bulgan River is a river in western Mongolia that flows through remote, sparsely populated steppe and mountain landscapes.
  • C. Tsenkher River
    The Tsenkher River is a Mongolian river that serves as one of the tributaries feeding the larger Kherlen River system.
  • D. Kherlen River
    The Kherlen River is a major river in eastern Mongolia that flows from the Khentii Mountains across the steppe toward China, supporting several towns and agricultural areas along its course.
  • E. Barguzin River
    The Barguzin River is a major river in eastern Siberia, Russia, that flows through the Barguzin Valley before emptying into Lake Baikal.
  • 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_69e2458750b481908a8e4cf4609cc6cf completed April 17, 2026, 2:36 p.m.
NER Named-entity recognition batch_69f17e89ab348190a31260221195ae67 completed April 29, 2026, 3:44 a.m.
Created at: April 17, 2026, 3:36 p.m.