Triple
T10784277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Upper Amuzgo |
E254411
|
entity |
| Predicate | hasAlternativeName |
P39
|
FINISHED |
| Object | High Amuzgo |
E254411
|
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: High Amuzgo | Statement: [Upper Amuzgo, hasAlternativeName, High Amuzgo]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: High Amuzgo Context triple: [Upper Amuzgo, hasAlternativeName, High Amuzgo]
-
A.
Upper Amuzgo
chosen
Upper Amuzgo is a variant of the Amuzgo language spoken by an indigenous community in southern Mexico.
-
B.
Amuzgo language
Amuzgo language is an indigenous Oto-Manguean language spoken primarily by the Amuzgo people in the states of Guerrero and Oaxaca in southern Mexico.
-
C.
Lower Amuzgo
Lower Amuzgo is a regional variety of the Amuzgo language spoken by indigenous communities in parts of southern Mexico.
-
D.
Aymara
Aymara is an indigenous language spoken primarily by the Aymara people of the central Andes in countries such as Bolivia, Peru, and Chile.
-
E.
Mochica language
The Mochica language is an extinct pre-Columbian language once spoken on the northern coast of Peru, associated with the Moche (Mochica) civilization.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 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_69d6aa609f008190a294200aefcb7bd5 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d732d2e7cc8190a4cb9a4d7c76ab15 |
completed | April 9, 2026, 5:02 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69de5609bf9c81908f47591f74c04701 |
completed | April 14, 2026, 2:58 p.m. |
Created at: April 8, 2026, 9:17 p.m.