Triple

T23094139
Position Surface form Disambiguated ID Type / Status
Subject Ralte language E575836 entity
Predicate isRelatedTo P37 FINISHED
Object Thado 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: Thado language | Statement: [Ralte language, isRelatedTo, Thado language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Thado language
Context triple: [Ralte language, isRelatedTo, Thado language]
  • A. Thavung language
    The Thavung language is a lesser-known Vietic language spoken by an ethnic minority community in parts of Laos and Vietnam.
  • B. Thadou language chosen
    Thadou language is a Kuki-Chin language spoken primarily by the Thadou people in northeastern India and neighboring regions.
  • C. Thao language
    Thao language is an endangered Formosan language of central Taiwan, traditionally spoken by the Thao people around Sun Moon Lake.
  • D. Thakri language
    Thakri is a lesser-known Southern Indo-Aryan language spoken by regional communities in the Indian subcontinent.
  • E. Ta-ang language
    The Ta-ang language is a Mon–Khmer language spoken primarily by the Ta-ang (Palaung) ethnic group in parts of Myanmar, China, and neighboring 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_69e245c060b48190a9bd61a47a16db17 completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f18de2ed088190971ff08c58b15aad completed April 29, 2026, 4:49 a.m.
Created at: April 17, 2026, 3:57 p.m.