Triple

T17483089
Position Surface form Disambiguated ID Type / Status
Subject Indigenous languages of California E425712 entity
Predicate hasLanguage P15 FINISHED
Object Serrano 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: Serrano language | Statement: [Indigenous languages of California, hasLanguage, Serrano language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Serrano language
Context triple: [Indigenous languages of California, hasLanguage, Serrano language]
  • A. Serrano language chosen
    The Serrano language is an endangered Uto-Aztecan Native American language traditionally spoken by the Serrano people of Southern California.
  • B. Cavineña language
    The Cavineña language is an indigenous Tacanan language spoken by the Cavineña people of northern Bolivia.
  • C. Ignaciano language
    The Ignaciano language is an Arawakan language spoken by the Ignaciano people of Bolivia’s Beni region, closely related to other Moxo (Mojeño) varieties.
  • D. Diegueño language
    The Diegueño language is a Yuman language traditionally spoken by the Kumeyaay (Diegueño) people of southern California and northern Baja California.
  • E. Tubares language
    The Tubares language is an extinct Uto-Aztecan language once spoken by the Tubar people in parts of northern Mexico.
  • 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_69d889dccf7481909264a1844a2e9100 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e451d06c2881909632845dd7a6b1e3 completed April 19, 2026, 3:53 a.m.
Created at: April 10, 2026, 5:48 a.m.