Triple

T15555194
Position Surface form Disambiguated ID Type / Status
Subject Southern Yana E370848 entity
Predicate subdivisionOf P258 FINISHED
Object Yana language E74837 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: Yana language | Statement: [Southern Yana, subdivisionOf, Yana language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Yana language
Context triple: [Southern Yana, subdivisionOf, Yana language]
  • A. Yana language chosen
    The Yana language is an extinct Native American language once spoken in northern California, notable for its complex verb morphology and documentation by linguist Edward Sapir.
  • B. Yatye language
    The Yatye language is a lesser-known Niger-Congo language spoken by a small community in Nigeria, belonging to the Idomoid branch.
  • C. Yamdena language
    The Yamdena language is an Austronesian language spoken primarily on Yamdena Island in Indonesia’s Tanimbar Islands.
  • D. Yakoma language
    The Yakoma language is a Ubangian language spoken by the Yakoma people of the Central African Republic and neighboring regions.
  • E. Yola language
    The Yola language was an extinct West Germanic language once spoken in County Wexford, Ireland, that preserved many archaic features derived from early English settlers.
  • 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_69d85cc6cf40819091f4a5facee1ebe6 completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69e04a97dbfc8190a98cbbac5e71ba88 completed April 16, 2026, 2:34 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff456209288190aba6debd434af741 completed May 9, 2026, 2:32 p.m.
Created at: April 10, 2026, 4:09 a.m.