Triple

T5361564
Position Surface form Disambiguated ID Type / Status
Subject Salar E103032 entity
Predicate language P15 FINISHED
Object Salar language E467177 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: Salar language | Statement: [Salar, language, Salar language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Salar language
Context triple: [Salar, language, Salar language]
  • A. Salar language chosen
    The Salar language is a Turkic language spoken primarily by the Salar people in northwestern China, notable for its Oghuz roots and heavy influence from Chinese and Tibetan.
  • B. Lasalimu language
    The Lasalimu language is an Austronesian language spoken by a small community on Buton Island in Southeast Sulawesi, Indonesia.
  • C. Saluan language
    The Saluan language is an Austronesian language spoken by the Saluan people of central and eastern Sulawesi, Indonesia.
  • D. Isnag language
    The Isnag language is an Austronesian language spoken by the Isnag people in the northern Cordillera region of Luzon in the Philippines.
  • E. Kalasha language
    The Kalasha language is an endangered Indo-Aryan language spoken by the Kalash people in the remote valleys of Chitral District in northern Pakistan.
  • 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_69bd43daa3e4819090b59d127db70e57 completed March 20, 2026, 12:55 p.m.
NER Named-entity recognition batch_69bd865a0bb081909579cfe7c7974075 completed March 20, 2026, 5:39 p.m.
NED1 Entity disambiguation (via context triple) batch_69bf291c89c8819084b9305c3bddc3c0 completed March 21, 2026, 11:26 p.m.
Created at: March 20, 2026, 2:02 p.m.