Triple

T4826028
Position Surface form Disambiguated ID Type / Status
Subject Northern Pakistan E107825 entity
Predicate hasLanguage P15 FINISHED
Object Balti language E375700 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: Balti language | Statement: [Northern Pakistan, hasLanguage, Balti language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Balti language
Context triple: [Northern Pakistan, hasLanguage, Balti language]
  • A. Balti language chosen
    The Balti language is a Tibetic language spoken primarily in the Baltistan region of northern Pakistan, known for preserving many archaic features of Classical Tibetan.
  • B. Boro language
    Boro language is a Tibeto-Burman language spoken primarily by the Boro people of Assam in northeastern India.
  • C. Zambal language
    Zambal language is an Austronesian language spoken by the Sambal people primarily in the Zambales region of the Philippines.
  • D. Balti
    Balti is a Tibetic language spoken primarily in the Baltistan region of northern Pakistan and parts of Ladakh, India.
  • E. Pajalate language
    The Pajalate language is an extinct indigenous language once spoken in what is now southern Texas and northeastern Mexico, traditionally classified within the Coahuiltecan language group.
  • 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_69bd43fac8188190803f0327190621e4 completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd6caf22308190a2048ec6acfa5af2 completed March 20, 2026, 3:50 p.m.
NED1 Entity disambiguation (via context triple) batch_69be4dcd3ecc8190a5223f00344019ff completed March 21, 2026, 7:50 a.m.
Created at: March 20, 2026, 1:24 p.m.