Triple

T19791725
Position Surface form Disambiguated ID Type / Status
Subject Chinggis City E475426 entity
Predicate hasAlternativeName P39 FINISHED
Object Öndörkhaan 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: Öndörkhaan | Statement: [Chinggis City, hasAlternativeName, Öndörkhaan]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Öndörkhaan
Context triple: [Chinggis City, hasAlternativeName, Öndörkhaan]
  • A. Ulaangom
    Ulaangom is a small provincial capital in northwestern Mongolia, known for its remote location near the Russian border and Lake Uvs.
  • B. Öndörkhaan, Mongolia chosen
    Öndörkhaan is a town in eastern Mongolia known historically as the site where Chinese marshal Lin Biao died in a 1971 plane crash.
  • C. 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.
  • D. Ulaanbaatar
    Ulaanbaatar is the capital and largest city of Mongolia, serving as its political, economic, and cultural center.
  • E. Хан-Уул дүүрэг
    Хан-Уул дүүрэг is one of the central districts of Ulaanbaatar, Mongolia, known for encompassing both urban neighborhoods and parts of the Bogd Khan Mountain national park area.
  • 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_69d8e51b014081908b263e167370529a completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e653c37a3c819080f195d58adaaa7b completed April 20, 2026, 4:26 p.m.
Created at: April 10, 2026, 1:49 p.m.