Triple
T7056172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maipurean languages |
E164095
|
entity |
| Predicate | member |
P10
|
FINISHED |
| Object | Yucuna language |
E168446
|
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: Yucuna language | Statement: [Maipurean languages, member, Yucuna language]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yucuna language Context triple: [Maipurean languages, member, Yucuna language]
-
A.
Yucuna language
chosen
The Yucuna language is an indigenous Arawakan language spoken by the Yucuna people of the Colombian Amazon.
-
B.
Yukpa language
The Yukpa language is an indigenous Cariban language spoken by the Yukpa people in the border regions of northeastern Colombia and western Venezuela.
-
C.
Wayana language
The Wayana language is an indigenous Cariban language spoken by the Wayana people of the Guiana region in northeastern South America.
-
D.
Piapoco language
The Piapoco language is an indigenous Arawakan language spoken by the Piapoco people of Colombia and Venezuela.
-
E.
Tsimané language
The Tsimané language is an indigenous South American language of the Mosetenan family spoken by the Tsimané people of Bolivia’s Amazonian lowlands.
- 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_69c68861678881909961ddf4d779f750 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e269050c81908c186609a8a7bcf9 |
completed | March 27, 2026, 8:02 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7944809348190bfc96df73f1363b3 |
completed | March 28, 2026, 8:41 a.m. |
Created at: March 27, 2026, 2:38 p.m.