Triple

T17387619
Position Surface form Disambiguated ID Type / Status
Subject Saluan people E422727 entity
Predicate language P15 FINISHED
Object Saluan 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: Saluan language | Statement: [Saluan people, language, Saluan language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Saluan language
Context triple: [Saluan people, language, Saluan language]
  • A. Saluan language chosen
    The Saluan language is an Austronesian language spoken by the Saluan people of central and eastern Sulawesi, Indonesia.
  • B. Kalanguya language
    The Kalanguya language is an Austronesian language spoken by the Kalanguya people in the northern Luzon highlands of the Philippines.
  • C. Luvale language
    The Luvale language is a Bantu language spoken primarily by the Luvale people of northwestern Zambia and eastern Angola.
  • D. Agutaynen language
    Agutaynen is an Austronesian language spoken by the Agutaynen people of Palawan in the Philippines.
  • E. Sa’och language
    The Sa’och language is an endangered Austroasiatic language spoken by the Sa’och people of Cambodia and Thailand, belonging to the Pearic branch.
  • 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_69d889d710288190bf0f4762801fefae completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e43a8b66288190b29bb82eff761902 completed April 19, 2026, 2:14 a.m.
Created at: April 10, 2026, 5:45 a.m.