Triple

T20933263
Position Surface form Disambiguated ID Type / Status
Subject Ölgii E515519 entity
Predicate roadConnection P385 FINISHED
Object Khovd 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: Khovd | Statement: [Ölgii, roadConnection, Khovd]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Khovd
Context triple: [Ölgii, roadConnection, Khovd]
  • A. Khovd chosen
    Khovd is a historically significant city in western Mongolia that serves as a regional cultural and economic center near the Altai Mountains.
  • B. Khorol
    Khorol is a town in central Ukraine historically situated within the former Poltava Governorate of the Russian Empire.
  • C. Toktogul
    Toktogul is a town in central Kyrgyzstan known for its proximity to the Toktogul Reservoir and its role in regional hydropower and agriculture.
  • D. Ghalghai
    Ghalghai is the self-designation of the Ingush people, a Northeast Caucasian ethnic group native to the North Caucasus region of Russia.
  • E. Kharkhorin
    Kharkhorin is a town in central Mongolia located near the ruins of the ancient Mongol capital Karakorum and serves as a gateway to the historic Orkhon Valley.
  • 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_69e0b4fb431c8190b9d40e6a72f0cc87 completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6f94e980c819083280a9c35af5930 completed April 21, 2026, 4:13 a.m.
Created at: April 16, 2026, 12:49 p.m.