Triple
T6427555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mochica language |
E128096
|
entity |
| Predicate | alternativeName |
P39
|
FINISHED |
| Object |
Yunca
Yunca is an alternative name for the extinct Mochica language once spoken on Peru’s northern coast.
|
E592982
|
NE FINISHED |
How this triple was built (4 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: Yunca | Statement: [Mochica language, alternativeName, Yunca]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yunca Context triple: [Mochica language, alternativeName, Yunca]
-
A.
Tangut
Tangut is an extinct Tibeto-Burman language once used in the Western Xia dynasty, best known today for its large and complex logographic writing system.
-
B.
Chochenyo
Chochenyo is an indigenous Ohlone language traditionally spoken in the East Bay region of the San Francisco Bay Area in California.
-
C.
Queyu language
The Queyu language is a lesser-known Sino-Tibetan tongue spoken by the Queyu (Choyo) people of western Sichuan, China, and is closely related to other Qiangic languages.
-
D.
Griko
Griko is a Greek-derived minority language spoken by communities in southern Italy, particularly in parts of Apulia and Calabria.
-
E.
Kankana-ey
Kankana-ey is an Austronesian language spoken by the Kankanaey people of the northern Philippines, particularly in the Cordillera region of Luzon.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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: Yunca Triple: [Mochica language, alternativeName, Yunca]
Generated description
Yunca is an alternative name for the extinct Mochica language once spoken on Peru’s northern coast.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Yunca Target entity description: Yunca is an alternative name for the extinct Mochica language once spoken on Peru’s northern coast.
-
A.
Tangut
Tangut is an extinct Tibeto-Burman language once used in the Western Xia dynasty, best known today for its large and complex logographic writing system.
-
B.
Chochenyo
Chochenyo is an indigenous Ohlone language traditionally spoken in the East Bay region of the San Francisco Bay Area in California.
-
C.
Queyu language
The Queyu language is a lesser-known Sino-Tibetan tongue spoken by the Queyu (Choyo) people of western Sichuan, China, and is closely related to other Qiangic languages.
-
D.
Griko
Griko is a Greek-derived minority language spoken by communities in southern Italy, particularly in parts of Apulia and Calabria.
-
E.
Kankana-ey
Kankana-ey is an Austronesian language spoken by the Kankanaey people of the northern Philippines, particularly in the Cordillera region of Luzon.
- F. None of above. chosen
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_69c00838de888190af2eec0b80495efa |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c06920cef48190a884df8f12987a0d |
completed | March 22, 2026, 10:11 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c640e339108190bbb74c688de574cc |
completed | March 27, 2026, 8:33 a.m. |
| NEDg | Description generation | batch_69c644a514f48190832bd628a071be46 |
completed | March 27, 2026, 8:49 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69c64527d1f88190b3b6f9a455f4ffce |
completed | March 27, 2026, 8:51 a.m. |
Created at: March 22, 2026, 4:44 p.m.