Triple

T35901558
Position Surface form Disambiguated ID Type / Status
Subject Tarahumaran E1038363 entity
Predicate alternativeName P39 FINISHED
Object Rarámuri languages
The Rarámuri languages are a group of closely related Uto-Aztecan indigenous languages spoken primarily by the Rarámuri (Tarahumara) people in northern Mexico.
E2161024 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: Rarámuri languages | Statement: [Tarahumaran, alternativeName, Rarámuri languages]
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: Rarámuri languages
Triple: [Tarahumaran, alternativeName, Rarámuri languages]
Generated description
The Rarámuri languages are a group of closely related Uto-Aztecan indigenous languages spoken primarily by the Rarámuri (Tarahumara) people in northern Mexico.

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_69f76e2190f88190beb2eed798a4ef01 completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69f7aa6a6a608190b0bd7ff2a949be5a completed May 3, 2026, 8:04 p.m.
NED1 Entity disambiguation (via context triple) batch_6a38ae2578a48190b08a987768507cd6 completed June 22, 2026, 3:38 a.m.
NEDg Description generation batch_6a38af1690f8819086cc6e77bfab4ccd completed June 22, 2026, 3:42 a.m.
NED2 Entity disambiguation (via description) batch_6a38afae6574819096f015f9d1c3eaca completed June 22, 2026, 3:44 a.m.
Created at: May 3, 2026, 4:07 p.m.