Triple

T22652581
Position Surface form Disambiguated ID Type / Status
Subject Achomi people E559131 entity
Predicate ethnonym P4709 FINISHED
Object Khonji 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: Khonji | Statement: [Achomi people, ethnonym, Khonji]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Khonji
Context triple: [Achomi people, ethnonym, Khonji]
  • A. Khonji chosen
    Khonji is an alternative name for the Achomi language, an Iranian language spoken primarily in southern Iran and by diaspora communities in the Persian Gulf region.
  • B. Khonj
    Khonj is a city in southern Iran known for its location in Fars Province and its predominantly Sunni Muslim population within a largely Shia region.
  • C. Thakore
    Thakore is a hereditary royal title used by certain princely rulers in the Kathiawar region of Gujarat, India.
  • D. Khoiniki
    Khoiniki is a town in southeastern Belarus known for its proximity to the Chernobyl-affected areas and its role in regional administration and services.
  • E. Khokana
    Khokana is a traditional Newar village in the Kathmandu Valley of Nepal, renowned for its historic architecture, unique cultural practices, and centuries-old mustard oil production.
  • 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_69e245489dd88190b1f674acf61c8769 completed April 17, 2026, 2:35 p.m.
NER Named-entity recognition batch_69f1703d7d648190aafe275cd04c47cf completed April 29, 2026, 2:43 a.m.
Created at: April 17, 2026, 3:06 p.m.