Triple

T22849270
Position Surface form Disambiguated ID Type / Status
Subject Jingpo people E566312 entity
Predicate speaks P741 FINISHED
Object Jingpho 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: Jingpho language | Statement: [Jingpo people, speaks, Jingpho language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Jingpho language
Context triple: [Jingpo people, speaks, Jingpho language]
  • A. Jingpho language chosen
    The Jingpho language is a Tibeto-Burman language spoken primarily by the Jingpo (Kachin) people of northern Myanmar and adjacent regions of China and India.
  • B. Khaling language
    The Khaling language is a Kiranti Sino-Tibetan language spoken by the Khaling ethnic group in eastern Nepal, noted for its complex verbal morphology and rich consonant system.
  • C. Chepang language
    The Chepang language is a Sino-Tibetan language spoken by the Chepang ethnic group in central Nepal, known for its complex phonology and endangered status.
  • D. Yamphu language
    The Yamphu language is a Kiranti Sino-Tibetan language spoken by the Yamphu ethnic community in eastern Nepal.
  • E. Phom language
    Phom language is a Sino-Tibetan language spoken primarily by the Phom Naga people in Nagaland, northeastern India.
  • 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_69e2458750b481908a8e4cf4609cc6cf completed April 17, 2026, 2:36 p.m.
NER Named-entity recognition batch_69f17e8aceb88190b137d17a7510fee4 completed April 29, 2026, 3:44 a.m.
Created at: April 17, 2026, 3:36 p.m.