Triple

T4838106
Position Surface form Disambiguated ID Type / Status
Subject Öndörkhaan Airport E108111 entity
Predicate serves P98 FINISHED
Object Öndörkhaan E108111 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: Öndörkhaan | Statement: [Öndörkhaan Airport, serves, Öndörkhaan]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Öndörkhaan
Context triple: [Öndörkhaan Airport, serves, Öndörkhaan]
  • A. Ö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.
  • B. 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.
  • C. Ulaanbaatar
    Ulaanbaatar is the capital and largest city of Mongolia, serving as its political, economic, and cultural center.
  • D. Hulunbuir
    Hulunbuir is a vast prefecture-level city in northeastern China renowned for its expansive grasslands, diverse ethnic cultures, and rich natural resources.
  • E. Borjigin
    Borjigin is the royal clan of Genghis Khan and his descendants, forming the ruling lineage of the Mongol Empire and several successor states.
  • 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_69bd43fbe444819085cb970706ef73f7 completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd6ce2e810819089f9a3f2a7574d44 completed March 20, 2026, 3:50 p.m.
NED1 Entity disambiguation (via context triple) batch_69be67d449188190a2f02fa30aee4891 completed March 21, 2026, 9:41 a.m.
Created at: March 20, 2026, 1:25 p.m.