Triple

T24201061
Position Surface form Disambiguated ID Type / Status
Subject Otomian E599979 entity
Predicate hasPart P35 FINISHED
Object Ocuilteco language
The Ocuilteco language is an indigenous Oto-Manguean language of central Mexico, traditionally spoken by the Ocuilteco people and now considered highly endangered or extinct.
E1655687 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: Ocuilteco language | Statement: [Otomian, hasPart, Ocuilteco language]
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: Ocuilteco language
Triple: [Otomian, hasPart, Ocuilteco language]
Generated description
The Ocuilteco language is an indigenous Oto-Manguean language of central Mexico, traditionally spoken by the Ocuilteco people and now considered highly endangered or extinct.

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_69e288ceaab88190899d0acb5931591d completed April 17, 2026, 7:23 p.m.
NER Named-entity recognition batch_69f27ca1f3b481908c14052a8435fd21 completed April 29, 2026, 9:48 p.m.
NED1 Entity disambiguation (via context triple) batch_6a1032da1ed48190b9c4fa303859b345 completed May 22, 2026, 10:41 a.m.
NEDg Description generation batch_6a1033ece8248190bc0ee7fa4976848d completed May 22, 2026, 10:46 a.m.
NED2 Entity disambiguation (via description) batch_6a10348fb55c819087a28d4a7280589c completed May 22, 2026, 10:48 a.m.
Created at: April 17, 2026, 11:36 p.m.