Triple
T22472518
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tacana people |
E555539
|
entity |
| Predicate | language |
P15
|
FINISHED |
| Object | Tacana language |
—
|
NE NERFINISHED |
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: Tacana language | Statement: [Tacana people, language, Tacana language]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tacana language Context triple: [Tacana people, language, Tacana language]
-
A.
Tacana language
chosen
The Tacana language is an indigenous Tacanan language spoken by the Tacana people of northern Bolivia, particularly in the Amazonian lowlands.
-
B.
Piapoco language
The Piapoco language is an indigenous Arawakan language spoken by the Piapoco people of Colombia and Venezuela.
-
C.
Tepehuán language
The Tepehuán language is a Uto-Aztecan indigenous language of northern Mexico spoken by the Tepehuán people in several regional dialects.
-
D.
Picurís language
The Picurís language is a Native American Tanoan language traditionally spoken by the Picurís Pueblo people of northern New Mexico and now considered highly endangered.
-
E.
Cavineña language
The Cavineña language is an indigenous Tacanan language spoken by the Cavineña people of northern Bolivia.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e11e52c2048190952dc5df209b9bed |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15be0d3c08190851537660cda619c |
completed | April 29, 2026, 1:16 a.m. |
Created at: April 16, 2026, 8:49 p.m.