Triple

T11372682
Position Surface form Disambiguated ID Type / Status
Subject Tuul River E269381 entity
Predicate flowsThrough P225 FINISHED
Object Ulaanbaatar E24958 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: Ulaanbaatar | Statement: [Tuul River, flowsThrough, Ulaanbaatar]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ulaanbaatar
Context triple: [Tuul River, flowsThrough, Ulaanbaatar]
  • A. Ulaanbaatar chosen
    Ulaanbaatar is the capital and largest city of Mongolia, serving as its political, economic, and cultural center.
  • B. Ulanhot
    Ulanhot is a county-level city in northeastern Inner Mongolia, China, known as a regional political and economic center and as the birthplace of the Inner Mongolia Autonomous Region.
  • C. Xilinhot
    Xilinhot is a city in Inner Mongolia, China, known as an important regional center on the Xilingol grasslands with a strong pastoral and Mongolian cultural heritage.
  • D. Ulanqab
    Ulanqab is a prefecture-level city in central Inner Mongolia, China, known for its grassland landscapes, agriculture, and strategic position as a transportation hub.
  • E. Hohhot
    Hohhot is the capital and largest city of Inner Mongolia in northern China, known as a regional center of politics, culture, and industry.
  • 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_69d6aacca1048190b39dbbc2174616fa completed April 8, 2026, 7:21 p.m.
NER Named-entity recognition batch_69d7ea8d244c8190b865260338edb532 completed April 9, 2026, 6:06 p.m.
NED1 Entity disambiguation (via context triple) batch_69e5568516a481909ea66cbe53968e84 completed April 19, 2026, 10:26 p.m.
Created at: April 8, 2026, 9:33 p.m.