Triple
T4026796
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mexican Cocopa |
E83609
|
entity |
| Predicate | hasAlternativeName |
P39
|
FINISHED |
| Object | Cocopa mexicano |
E83609
|
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: Cocopa mexicano | Statement: [Mexican Cocopa, hasAlternativeName, Cocopa mexicano]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Cocopa mexicano Context triple: [Mexican Cocopa, hasAlternativeName, Cocopa mexicano]
-
A.
U.S. Cocopa
U.S. Cocopa is a regional dialect of the Cocopa language spoken by Cocopah communities in the United States.
-
B.
Tecuala
Tecuala is a municipality and town in the Mexican state of Nayarit, known for its agricultural activities and proximity to coastal wetlands along the Pacific.
-
C.
Tocopilla
Tocopilla is a coastal city and port in northern Chile known for its mining industry and location on the Pacific Ocean.
-
D.
Zapote
Zapote is a district of San José, Costa Rica, known for housing important government buildings and urban residential areas.
-
E.
Mexican Cocopa
chosen
Mexican Cocopa is a regional variety of the Cocopa language spoken by Cocopa communities in northern 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_69aed92e29ac819080f7a98b594fec05 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefaed37e48190844032e7e77163e0 |
completed | March 9, 2026, 4:53 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b562948c9081909054a756794e8576 |
completed | March 14, 2026, 1:28 p.m. |
Created at: March 9, 2026, 3:36 p.m.