Triple

T14933984
Position Surface form Disambiguated ID Type / Status
Subject Ishkashimi E372341 entity
Predicate closelyRelatedTo P37 FINISHED
Object Sanglechi E228137 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: Sanglechi | Statement: [Ishkashimi, closelyRelatedTo, Sanglechi]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sanglechi
Context triple: [Ishkashimi, closelyRelatedTo, Sanglechi]
  • A. Sanglechi chosen
    Sanglechi is a lesser-known Eastern Iranian language spoken in parts of northeastern Afghanistan and adjacent regions.
  • B. Oshikwambi
    Oshikwambi is a regional dialect of the Oshiwambo language spoken by the Kwambi people in northern Namibia.
  • C. Garango
    Garango is a town in Burkina Faso known for its cultural and municipal ties with the German town of Ladenburg.
  • D. Kasangati
    Kasangati is a town in central Uganda that serves as a growing commercial and residential hub within the Greater Kampala metropolitan area.
  • E. Chambeali
    Chambeali is an Indo-Aryan language spoken primarily in the Chamba region of Himachal Pradesh in northern India.
  • 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_69d85cc9da0c81908d583ca3f63a3908 completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69ded646a0808190ba5c0c91bde011c5 completed April 15, 2026, 12:05 a.m.
NED1 Entity disambiguation (via context triple) batch_69fe968bbbac8190a258c42b226f9def completed May 9, 2026, 2:06 a.m.
Created at: April 10, 2026, 2:37 a.m.