Triple

T22169752
Position Surface form Disambiguated ID Type / Status
Subject Kumul Rebellion E547887 entity
Predicate location P40 FINISHED
Object Hami 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: Hami | Statement: [Kumul Rebellion, location, Hami]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hami
Context triple: [Kumul Rebellion, location, Hami]
  • A. Hami chosen
    Hami is a city in eastern Xinjiang, China, historically known as an important Silk Road oasis and for producing the famous Hami melon.
  • B. Hushe
    Hushe is a remote village in Pakistan’s Karakoram region that serves as a key gateway for trekkers and climbers heading toward major peaks and glaciers.
  • C. Ghomari
    Ghomari is an alternative name for the Ghomara language, a Northern Berber language spoken by the Ghomara people in northern Morocco.
  • D. Rushan
    Rushan is a county-level coastal city in eastern Shandong Province, China, known for its fishing industry, beaches, and marine-based economy.
  • E. Khar
    Khar is a suburban neighborhood in Mumbai, India, known for its residential areas, shopping streets, and proximity to the Arabian Sea.
  • 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_69e11e3c4c5c81908d336165816b12e0 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f12a67f4dc81909cc5f8d2c1fe6129 completed April 28, 2026, 9:45 p.m.
Created at: April 16, 2026, 8:34 p.m.