Triple

T8235525
Position Surface form Disambiguated ID Type / Status
Subject Chifeng E192395 entity
Predicate hasAlternativeName P39 FINISHED
Object Ulankhad E205471 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: Ulankhad | Statement: [Chifeng, hasAlternativeName, Ulankhad]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ulankhad
Context triple: [Chifeng, hasAlternativeName, Ulankhad]
  • A. Ulanqab chosen
    Ulanqab is a prefecture-level city in central Inner Mongolia, China, known for its grassland landscapes, agriculture, and strategic position as a transportation hub.
  • B. Öndörkhaan, Mongolia
    Ö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. Borjigin
    Borjigin is the royal clan of Genghis Khan and his descendants, forming the ruling lineage of the Mongol Empire and several successor states.
  • D. Selenge
    Selenge is a northern Mongolian province (aimag) known for its agricultural lands and strategic location along the border with Russia.
  • E. Khorol
    Khorol is a town in central Ukraine historically situated within the former Poltava Governorate of the Russian Empire.
  • 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_69ca82dc8f148190a2c75a98501a7b91 completed March 30, 2026, 2:04 p.m.
NER Named-entity recognition batch_69cb782931848190bcc54622f34e06a7 completed March 31, 2026, 7:30 a.m.
NED1 Entity disambiguation (via context triple) batch_69cd94e168688190aa0a7149a4f8c4b0 completed April 1, 2026, 9:57 p.m.
Created at: March 30, 2026, 5:46 p.m.