Triple

T23505230
Position Surface form Disambiguated ID Type / Status
Subject Yamphu language E572262 entity
Predicate neighboringLanguage P16383 FINISHED
Object Yakkha 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: Yakkha language | Statement: [Yamphu language, neighboringLanguage, Yakkha language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Yakkha language
Context triple: [Yamphu language, neighboringLanguage, Yakkha language]
  • A. Yakkha language chosen
    Yakkha language is a Sino-Tibetan language spoken by the Yakkha people of eastern Nepal and classified within the Kiranti branch.
  • B. Yakoma language
    The Yakoma language is a Ubangian language spoken by the Yakoma people of the Central African Republic and neighboring regions.
  • C. Yavitero language
    The Yavitero language is an extinct Arawakan language once spoken by the Yavitero people along the Orinoco River region of Venezuela and Colombia.
  • D. Yaur language
    The Yaur language is an Austronesian language spoken by an indigenous community in the South Halmahera–West New Guinea region of eastern Indonesia.
  • E. Karkar-Yuri language
    Karkar-Yuri is a Papuan language of Papua New Guinea, spoken by the Karkar and Yuri peoples in the Sepik region.
  • 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_69e245b5e4208190bac8a6509867e394 completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f1a8ff97c88190a67f787e1674619e completed April 29, 2026, 6:45 a.m.
Created at: April 17, 2026, 6:07 p.m.