Triple

T31231318
Position Surface form Disambiguated ID Type / Status
Subject Rengma Naga tribe E796288 entity
Predicate secondaryLanguageUse P9103 FINISHED
Object English LITERAL 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: English | Statement: [Rengma Naga tribe, secondaryLanguageUse, English]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: secondaryLanguageUse
Context triple: [Rengma Naga tribe, secondaryLanguageUse, English]
  • A. secondaryLanguageSupport
    Indicates that an entity provides assistance, services, or functionality in an additional (non-primary) language.
  • B. secondaryLanguageContext
    Indicates that the associated information, interaction, or content occurs within or is tailored to a secondary (non-primary) language setting or usage context.
  • C. hasSecondaryLanguage chosen
    Indicates that an entity possesses or uses a secondary language in addition to its primary language.
  • D. laterLanguageDominant
    Indicates that one language becomes the dominant or primary language for an entity at a later point in time, after another language previously held that role.
  • E. hasSecondaryNationalLanguage
    Indicates that an entity possesses an officially recognized secondary national language in addition to its primary national language.
  • F. None of above.

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_69f224da98f88190ab32f690cce5d303 completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69fe08d2b2e48190ac7be6d62d4a44a3 completed May 8, 2026, 4:01 p.m.
PD Predicate disambiguation batch_69fe06cd3af08190ae25de0dc0cdd573 completed May 8, 2026, 3:52 p.m.
Created at: April 29, 2026, 9:10 p.m.