Triple

T10909707
Position Surface form Disambiguated ID Type / Status
Subject Chicham languages E257662 entity
Predicate hasMemberLanguage P7390 FINISHED
Object Awajún language E256707 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: Awajún language | Statement: [Chicham languages, hasMemberLanguage, Awajún language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Awajún language
Context triple: [Chicham languages, hasMemberLanguage, Awajún language]
  • A. Awajún language chosen
    Awajún language is an indigenous Jivaroan language spoken primarily by the Awajún (Aguaruna) people of northern Peru.
  • B. Enawené-Nawé language
    The Enawené-Nawé language is an indigenous Arawakan language spoken by the Enawené-Nawé people of the Brazilian Amazon, known for its highly endangered status and rich oral tradition.
  • C. Yucuna language
    The Yucuna language is an indigenous Arawakan language spoken by the Yucuna people of the Colombian Amazon.
  • 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_69d6aa8550c8819095508a2ed9acf3db completed April 8, 2026, 7:20 p.m.
NER Named-entity recognition batch_69d77068e5488190bbc881ebf51d6b2e completed April 9, 2026, 9:24 a.m.
NED1 Entity disambiguation (via context triple) batch_69e42d4ab9bc81908a2522d1334390fc completed April 19, 2026, 1:18 a.m.
Created at: April 8, 2026, 9:22 p.m.