Triple

T21870475
Position Surface form Disambiguated ID Type / Status
Subject Truku E539986 entity
Predicate language P15 FINISHED
Object Truku 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: Truku language | Statement: [Truku, language, Truku language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Truku language
Context triple: [Truku, language, Truku language]
  • A. Truku language chosen
    The Truku language is an indigenous Austronesian language of the Truku people in eastern Taiwan, noted for its complex phonology and endangered status.
  • B. Kavalan language
    The Kavalan language is an endangered Austronesian language of the indigenous Kavalan people of northeastern Taiwan.
  • C. Rukai language
    The Rukai language is an Austronesian language spoken by the Rukai people of southern Taiwan, known for its complex phonology and rich system of honorifics.
  • D. Atayal language
    The Atayal language is an Austronesian language spoken by the Atayal indigenous people of northern Taiwan, known for its complex verb morphology and rich system of focus and voice.
  • E. Tipra language
    Tipra language, also known as Kokborok, is a Tibeto-Burman language spoken primarily by the Tripuri people of the Indian state of Tripura and surrounding regions.
  • 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_69e0c478f59081909d54302b57fc1ce3 completed April 16, 2026, 11:14 a.m.
NER Named-entity recognition batch_69f0f33509d08190b33775abb84d5255 completed April 28, 2026, 5:49 p.m.
Created at: April 16, 2026, 6:57 p.m.