Triple

T21718260
Position Surface form Disambiguated ID Type / Status
Subject Gaddi language E536086 entity
Predicate writingSystem P454 FINISHED
Object Takri 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: Takri | Statement: [Gaddi language, writingSystem, Takri]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Takri
Context triple: [Gaddi language, writingSystem, Takri]
  • A. Takri script chosen
    The Takri script is an abugida historically used in the western Himalayas, particularly in regions of present-day Himachal Pradesh and Jammu, to write several Indo-Aryan languages such as Dogri and Jaunsari.
  • B. Bukharic
    Bukharic is a Jewish dialect of Tajik spoken historically by the Bukharan Jewish community of Central Asia.
  • C. Ganjami
    Ganjami is a regional dialect of the Odia language spoken primarily in the Ganjam region of Odisha, India.
  • D. Ruqʿah script
    Ruqʿah script is a simple, highly legible Arabic handwriting style commonly used for everyday writing and official documents in the Arab world.
  • E. Khojki script
    The Khojki script is a historical writing system used primarily by the Nizari Ismaili community of South Asia to record religious and literary texts in languages such as Sindhi and Gujarati.
  • 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_69e0c46c6dd88190a595375fa6ebd701 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69efd96cc58081908dda09819041b888 completed April 27, 2026, 9:47 p.m.
Created at: April 16, 2026, 6:47 p.m.