Triple
T14514313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Core Yuman |
E340477
|
entity |
| Predicate | hasPart |
P35
|
FINISHED |
| Object | Cocopa language |
E13260
|
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 language | Statement: [Core Yuman, hasPart, Cocopa language]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Cocopa language Context triple: [Core Yuman, hasPart, Cocopa language]
-
A.
Cocopa language
chosen
The Cocopa language is an indigenous Native American language spoken by the Cocopah people of the lower Colorado River region in the United States and Mexico.
-
B.
Cochimí language
The Cochimí language is an extinct indigenous language once spoken by the Cochimí people of the central Baja California peninsula in Mexico.
-
C.
Cocama language
The Cocama language is an endangered indigenous Tupian language spoken by the Cocama-Cocamilla people in the Amazon regions of Peru, Brazil, and Colombia.
-
D.
Piapoco language
The Piapoco language is an indigenous Arawakan language spoken by the Piapoco people of Colombia and Venezuela.
-
E.
Cuicatec language
The Cuicatec language is an indigenous Oto-Manguean language of Mexico spoken primarily in northern Oaxaca.
- 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_69d822d9c0408190b9a2b3643e58bb4d |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69de9a6d82988190b6f957012bcc63d4 |
completed | April 14, 2026, 7:50 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd6da64db881909a4f88d18031cb0c |
completed | May 8, 2026, 4:59 a.m. |
Created at: April 10, 2026, 1:21 a.m.