Triple

T6301126
Position Surface form Disambiguated ID Type / Status
Subject Truku language E141256 entity
Predicate subfamily P4180 FINISHED
Object Atayalic E138016 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: Atayalic | Statement: [Truku language, subfamily, Atayalic]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Atayalic
Context triple: [Truku language, subfamily, Atayalic]
  • A. Atayalic languages chosen
    The Atayalic languages are a small subgroup of indigenous Austronesian languages spoken in northern Taiwan, primarily by the Atayal and Seediq peoples.
  • B. Taracahitic
    Taracahitic is a proposed subgroup of the Uto-Aztecan language family that includes several indigenous languages once spoken in northwestern Mexico.
  • C. Tepiman languages
    The Tepiman languages are a group of closely related Uto-Aztecan indigenous languages spoken primarily in northern Mexico by various Tepehuán and Piman peoples.
  • D. Avikam language
    The Avikam language is a Kwa language spoken by the Avikam people of southern Côte d'Ivoire.
  • E. Amuesha language
    The Amuesha language, also known as Yanesha', is an Arawakan language spoken by the Yanesha' people of the central Peruvian Amazon.
  • 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_69c008cf0ad4819095def81e2bd42f9f completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c0645bb41481909294b06e2b3e1845 completed March 22, 2026, 9:51 p.m.
NED1 Entity disambiguation (via context triple) batch_69c5e42f38bc819086a3e66a83ffc792 completed March 27, 2026, 1:58 a.m.
Created at: March 22, 2026, 4:27 p.m.