Triple
T10447826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Costa Chica of Oaxaca |
E246338
|
entity |
| Predicate | languageSpoken |
P151
|
FINISHED |
| Object | Amuzgo language |
E254409
|
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: Amuzgo language | Statement: [Costa Chica of Oaxaca, languageSpoken, Amuzgo language]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Amuzgo language Context triple: [Costa Chica of Oaxaca, languageSpoken, Amuzgo language]
-
A.
Amuzgo language
chosen
Amuzgo language is an indigenous Oto-Manguean language spoken primarily by the Amuzgo people in the states of Guerrero and Oaxaca in southern Mexico.
-
B.
Guarijío language
The Guarijío language is an indigenous Uto-Aztecan language spoken by the Guarijío people of northern Mexico, particularly in the states of Chihuahua and Sonora.
-
C.
Piapoco language
The Piapoco language is an indigenous Arawakan language spoken by the Piapoco people of Colombia and Venezuela.
-
D.
Cuicatec language
The Cuicatec language is an indigenous Oto-Manguean language of Mexico spoken primarily in northern Oaxaca.
-
E.
Yucuna language
The Yucuna language is an indigenous Arawakan language spoken by the Yucuna people of the Colombian Amazon.
- 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_69d381c04fe08190957c26c526a3b05a |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4fdc10c8081908a3801fe1dea63de |
completed | April 7, 2026, 12:51 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d87ef4e0dc81908d7cf0f2b6f4cd98 |
completed | April 10, 2026, 4:39 a.m. |
Created at: April 6, 2026, 12:16 p.m.