Triple

T16708053
Position Surface form Disambiguated ID Type / Status
Subject Yana people E406023 entity
Predicate subgroup P10 FINISHED
Object Southern Yana E370848 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: Southern Yana | Statement: [Yana people, subgroup, Southern Yana]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Southern Yana
Context triple: [Yana people, subgroup, Southern Yana]
  • A. Southern Yana chosen
    Southern Yana is a now-extinct dialect of the Yana language once spoken by Indigenous people in northern California.
  • B. Northern Yana
    Northern Yana is a now-extinct dialect of the Yana language once spoken by Indigenous people in northern California.
  • C. Central Yana
    Central Yana were a Native American group of the Yana people of northern California, culturally and linguistically related to the Yahi.
  • D. Onon River region
    The Onon River region is a historical area in northeastern Mongolia and southeastern Russia known as the traditional homeland of Genghis Khan and the early Mongol tribes.
  • E. Northern Subanen
    Northern Subanen is a major dialect of the Subanen language spoken by Subanen communities in the northern regions of the Zamboanga Peninsula in the southern Philippines.
  • 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_69d8838db21081909589220fd71440a4 completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e38337ecac8190bc4a9410ed7681ab completed April 18, 2026, 1:12 p.m.
NED1 Entity disambiguation (via context triple) batch_6a00a51378788190b9f3bb0a344dcdd8 completed May 10, 2026, 3:32 p.m.
Created at: April 10, 2026, 5:20 a.m.