Triple

T1054912
Position Surface form Disambiguated ID Type / Status
Subject Xinjiang E22779 entity
Predicate containsCity P294 FINISHED
Object Hotan E128870 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: Hotan | Statement: [Xinjiang, containsCity, Hotan]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hotan
Context triple: [Xinjiang, containsCity, Hotan]
  • A. Hotan chosen
    Hotan is an oasis city in southwestern Xinjiang, China, historically known as a key Silk Road hub famed for its jade, silk, and carpets.
  • B. Kashgar
    Kashgar is an ancient oasis city in western China’s Xinjiang region that long served as a key cultural and commercial crossroads between East and West.
  • C. Korla
    Korla is a major oasis city in Xinjiang, China, known as an important transportation and economic hub along the northern edge of the Taklamakan Desert.
  • D. Khorgom
    Khorgom is a village in the Lake Van region of present-day eastern Turkey, historically part of Western Armenia and known as the birthplace of painter Arshile Gorky.
  • E. Turpan
    Turpan is an oasis city and depression in China’s Xinjiang region, historically a key Silk Road hub known for its extreme heat, ancient irrigation systems, and grape cultivation.
  • 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_69a493da02e081908c13ff5e02a0fe7a completed March 1, 2026, 7:30 p.m.
NER Named-entity recognition batch_69a4b8d79268819080f3f3f497e91c58 completed March 1, 2026, 10:08 p.m.
NED1 Entity disambiguation (via context triple) batch_69ac763827b08190b84cc18a5cfa64fc completed March 7, 2026, 7:02 p.m.
Created at: March 1, 2026, 7:42 p.m.