Triple

T22549882
Position Surface form Disambiguated ID Type / Status
Subject Salar people E557530 entity
Predicate language P15 FINISHED
Object Salar language 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: Salar language | Statement: [Salar people, language, Salar language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Salar language
Context triple: [Salar people, 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. Sar language
    Sar language is a Papuan language spoken on Pantar Island in eastern Indonesia, known for its complex verb morphology and membership in the Alor–Pantar language family.
  • E. Isnag language
    The Isnag language is an Austronesian language spoken by the Isnag people in the northern Cordillera region of Luzon in the Philippines.
  • 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_69e11e59db848190b4272ecd2b690ffd completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f15f74512c8190b5369e19a4bc6325 completed April 29, 2026, 1:31 a.m.
Created at: April 16, 2026, 8:52 p.m.