Triple

T9250637
Position Surface form Disambiguated ID Type / Status
Subject Reang language E222312 entity
Predicate alternateName P39 FINISHED
Object Riang language E775499 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: Riang language | Statement: [Reang language, alternateName, Riang language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Riang language
Context triple: [Reang language, alternateName, Riang language]
  • A. Riang language chosen
    The Riang language is an Austroasiatic language spoken by the Riang people of Myanmar and neighboring regions, belonging to the Palaungic branch and characterized by multiple dialects and significant contact influence from surrounding languages.
  • B. Reang language
    Reang language is a Tibeto-Burman tribal language spoken primarily by the Reang (Bru) community of Tripura and neighboring regions in Northeast India.
  • C. Nachiring language
    Nachiring language is a lesser-known Kiranti language spoken by the Nachiring people in eastern Nepal.
  • D. 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.
  • E. Baniwa language
    Baniwa is an Arawakan Indigenous language spoken primarily along the Rio Negro in northwestern Brazil, as well as in parts of Colombia and Venezuela.
  • 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_69ca841d2b18819089f9faf5b2c2aec0 completed March 30, 2026, 2:09 p.m.
NER Named-entity recognition batch_69cd05f9ade48190ac8425a1c6f066b1 completed April 1, 2026, 11:48 a.m.
NED1 Entity disambiguation (via context triple) batch_69d0780650648190bc85452678268134 completed April 4, 2026, 2:31 a.m.
Created at: March 30, 2026, 7:31 p.m.