Triple

T15780562
Position Surface form Disambiguated ID Type / Status
Subject Chochenyo Ohlone E382602 entity
Predicate language P15 FINISHED
Object Chochenyo language E362270 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: Chochenyo language | Statement: [Chochenyo Ohlone, language, Chochenyo language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Chochenyo language
Context triple: [Chochenyo Ohlone, language, Chochenyo language]
  • A. Chochenyo chosen
    Chochenyo is an indigenous Ohlone language traditionally spoken in the East Bay region of the San Francisco Bay Area in California.
  • B. Nyishi language
    The Nyishi language is a Tani (Tibeto-Burman) language spoken primarily by the Nyishi people of Arunachal Pradesh in northeastern India.
  • C. Yamphu language
    The Yamphu language is a Kiranti Sino-Tibetan language spoken by the Yamphu ethnic community in eastern Nepal.
  • D. Siwu language
    The Siwu language is a Niger-Congo language spoken primarily in the Volta Region of Ghana by the Mawu people.
  • E. Queyu language
    The Queyu language is a lesser-known Sino-Tibetan tongue spoken by the Queyu (Choyo) people of western Sichuan, China, and is closely related to other Qiangic languages.
  • 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_69d86da09a10819082fe9797b23e4664 completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e053fea90081908e3fe4f91475bead completed April 16, 2026, 3:14 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff909f7f4481909cceb32e26af3780 completed May 9, 2026, 7:53 p.m.
Created at: April 10, 2026, 4:48 a.m.