Triple

T22888350
Position Surface form Disambiguated ID Type / Status
Subject Namuyi language E567666 entity
Predicate spokenBy P2181 FINISHED
Object Namuyi people
The Namuyi people are an ethnic group of southwestern China, primarily in Sichuan and Yunnan, known for their distinct Tibeto-Burman language and traditional highland culture.
E1964140 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: Namuyi people | Statement: [Namuyi language, spokenBy, Namuyi people]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Namuyi people
Triple: [Namuyi language, spokenBy, Namuyi people]
Generated description
The Namuyi people are an ethnic group of southwestern China, primarily in Sichuan and Yunnan, known for their distinct Tibeto-Burman language and traditional highland culture.

Provenance (5 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_69e2458a92ec81908fc1cd5f6407d2ab completed April 17, 2026, 2:36 p.m.
NER Named-entity recognition batch_69f17fc2adb4819081bce7e6849ba31a completed April 29, 2026, 3:49 a.m.
NED1 Entity disambiguation (via context triple) batch_6a2b142a219c81908edd9b7929cbf450 completed June 11, 2026, 8:01 p.m.
NEDg Description generation batch_6a2b14d0baf48190972401056fe70454 completed June 11, 2026, 8:04 p.m.
NED2 Entity disambiguation (via description) batch_6a2b154762408190b18d62464e7faba0 completed June 11, 2026, 8:06 p.m.
Created at: April 17, 2026, 3:40 p.m.