Triple
T10784190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amuzgo language |
E254409
|
entity |
| Predicate | hasDialect |
P4251
|
FINISHED |
| Object | Southern Amuzgo |
E256257
|
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: Southern Amuzgo | Statement: [Amuzgo language, hasDialect, Southern Amuzgo]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Southern Amuzgo Context triple: [Amuzgo language, hasDialect, Southern Amuzgo]
-
A.
Northern Amuzgo
Northern Amuzgo is a major regional variety of the Amuzgo language spoken by indigenous Amuzgo communities in parts of southern Mexico.
-
B.
Upper Amuzgo
Upper Amuzgo is a variant of the Amuzgo language spoken by an indigenous community in southern Mexico.
-
C.
Quetzaltepec Mixe
Quetzaltepec Mixe is an indigenous Mixe language spoken primarily in the region around San Juan Quetzaltepec in Oaxaca, Mexico.
-
D.
Zapotec
The Zapotec are an indigenous Mesoamerican people primarily from the Oaxaca region of southern Mexico, known for their ancient civilization, distinctive language family, and rich cultural traditions.
-
E.
Lower Amuzgo
chosen
Lower Amuzgo is a regional variety of the Amuzgo language spoken by indigenous communities in parts of southern Mexico.
- 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_69de84c925088190922b9979cf77d01b |
completed | April 14, 2026, 6:17 p.m. |
Created at: April 8, 2026, 9:17 p.m.