Triple
T7056169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maipurean languages |
E164095
|
entity |
| Predicate | member |
P10
|
FINISHED |
| Object | Piapoco language |
E170152
|
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: Piapoco language | Statement: [Maipurean languages, member, Piapoco language]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Piapoco language Context triple: [Maipurean languages, member, Piapoco language]
-
A.
Piapoco language
chosen
The Piapoco language is an indigenous Arawakan language spoken by the Piapoco people of Colombia and Venezuela.
-
B.
Sipakapense language
The Sipakapense language is a Mayan language spoken by the Sipakapense people in the western highlands of Guatemala.
-
C.
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.
-
D.
Yucuna language
The Yucuna language is an indigenous Arawakan language spoken by the Yucuna people of the Colombian Amazon.
-
E.
Awajún language
Awajún language is an indigenous Jivaroan language spoken primarily by the Awajún (Aguaruna) people of northern Peru.
- 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_69c788a303148190869be2a455d28791 |
completed | March 28, 2026, 7:52 a.m. |
Created at: March 27, 2026, 2:38 p.m.