Triple

T21216278
Position Surface form Disambiguated ID Type / Status
Subject Gaochang E522842 entity
Predicate alsoKnownAs P39 FINISHED
Object Khocho 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: Khocho | Statement: [Gaochang, alsoKnownAs, Khocho]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Khocho
Context triple: [Gaochang, alsoKnownAs, Khocho]
  • A. Khocho chosen
    Khocho was an important ancient oasis city in the Turpan region of present-day Xinjiang, China, known as a key Silk Road hub and a major center of Buddhist culture and manuscripts.
  • B. Akhulgo
    Akhulgo was a heavily fortified mountain stronghold in Dagestan that served as Imam Shamil’s key base during the Murid War against the Russian Empire.
  • C. Qahhor
    Qahhor is a masculine given name commonly used in Central Asia, particularly in Tajik and Uzbek cultures.
  • D. Raqchi
    Raqchi is a significant Inca archaeological complex in Peru, known for its monumental Temple of Wiracocha and extensive ceremonial and residential structures.
  • E. Nushki
    Nushki is a town in Pakistan’s Balochistan province, known as a key junction on routes linking the region to Afghanistan and Iran.
  • 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_69e0b511ed84819099b449b4a111085c completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e73473870c8190a0f41f9c85567aa7 completed April 21, 2026, 8:25 a.m.
Created at: April 16, 2026, 3:41 p.m.