Triple

T23506223
Position Surface form Disambiguated ID Type / Status
Subject Mirish languages E572288 entity
Predicate hasMember P10 FINISHED
Object Pailibo 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: Pailibo language | Statement: [Mirish languages, hasMember, Pailibo language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Pailibo language
Context triple: [Mirish languages, hasMember, Pailibo language]
  • A. Pailibo language chosen
    The Pailibo language is a Tani (Tibeto-Burman) language spoken by the Pailibo people of Arunachal Pradesh in northeastern India.
  • B. Paite language
    The Paite language is a Tibeto-Burman language spoken primarily by the Paite people in northeastern India and parts of Myanmar.
  • C. Ipai language
    The Ipai language is a Native American language traditionally spoken by the Kumeyaay (Ipai) people of southern California and northern Baja California.
  • D. Kacipo-Bale language
    The Kacipo-Bale language is a Surmic language spoken by the Kacipo and Bale peoples of southwestern Ethiopia and neighboring regions of South Sudan.
  • E. Tubatulabal language
    The Tubatulabal language is an endangered Uto-Aztecan language traditionally spoken by the Tubatulabal people of the southern Sierra Nevada region in California.
  • 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_69f1a9009ca081908c4cffb8c32293ec completed April 29, 2026, 6:45 a.m.
Created at: April 17, 2026, 6:07 p.m.