Triple

T16494439
Position Surface form Disambiguated ID Type / Status
Subject Ghizer District E400645 entity
Predicate hasEthnicGroup P1898 FINISHED
Object Kho E950768 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: Kho | Statement: [Ghizer District, hasEthnicGroup, Kho]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kho
Context triple: [Ghizer District, hasEthnicGroup, Kho]
  • A. Kho chosen
    Kho is the ethnonym for an Indo-Aryan ethnic group primarily inhabiting the Chitral region of northern Pakistan, known for their distinct Kho language and culture.
  • B. Kha
    Kha was an ancient Egyptian architect and overseer of works during the 18th Dynasty, best known for his exceptionally well-preserved tomb and funerary assemblage discovered at Deir el-Medina.
  • C. Kha
    Kha is an alternative name or variant spelling of the ancient Egyptian concept of the "ka," the vital spiritual essence or life force of a person.
  • D. Kote
    Kote is a Georgian given name commonly used as a diminutive of Konstantine.
  • E. Kagee
    Kagee is the former name of Chiayi City, a historic urban center in southwestern Taiwan.
  • 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_69d88381f6148190819958a038be990e completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e32e3276b88190946a669b4d893a54 completed April 18, 2026, 7:09 a.m.
NED1 Entity disambiguation (via context triple) batch_6a005828849481909e95c5822ed6f74d completed May 10, 2026, 10:04 a.m.
Created at: April 10, 2026, 5:14 a.m.