Triple
T36118463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zoquean languages |
E1044673
|
entity |
| Predicate | hasLanguage |
P15
|
FINISHED |
| Object |
Ayapa Zoque
Ayapa Zoque is a critically endangered indigenous language of the Zoquean family traditionally spoken in the village of Ayapa in Tabasco, Mexico.
|
E2171168
|
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: Ayapa Zoque | Statement: [Zoquean languages, hasLanguage, Ayapa Zoque]
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: Ayapa Zoque Triple: [Zoquean languages, hasLanguage, Ayapa Zoque]
Generated description
Ayapa Zoque is a critically endangered indigenous language of the Zoquean family traditionally spoken in the village of Ayapa in Tabasco, 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_69f76e344a4c8190af3858c6d78ba88f |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b2cebe088190a9f85263549d81fb |
completed | May 3, 2026, 8:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a390d3e5e948190b20be728f76236ac |
completed | June 22, 2026, 10:23 a.m. |
| NEDg | Description generation | batch_6a390dadf9a881908f39c69eae2009d1 |
completed | June 22, 2026, 10:25 a.m. |
| NED2 | Entity disambiguation (via description) | batch_6a390e9b47608190bce85055453afcda |
completed | June 22, 2026, 10:29 a.m. |
Created at: May 3, 2026, 4:08 p.m.