Triple

T11228896
Position Surface form Disambiguated ID Type / Status
Subject Huambisa E265767 entity
Predicate closelyRelatedTo P37 FINISHED
Object Aguaruna E257472 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: Aguaruna | Statement: [Huambisa, closelyRelatedTo, Aguaruna]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Aguaruna
Context triple: [Huambisa, closelyRelatedTo, Aguaruna]
  • A. Aguaruna chosen
    Aguaruna are an Indigenous people of the Peruvian Amazon, known for their Jivaroan language, forest-based livelihoods, and strong traditions of autonomy and resistance.
  • B. Sácama
    Sácama is a small municipality located in the Casanare Department of eastern Colombia, known for its rural character and Andean–Orinoco transitional landscapes.
  • C. Jucuna
    Jucuna is an alternative name for the Yucuna language, an indigenous Arawakan language spoken in the Amazon region of Colombia.
  • D. Achacachi
    Achacachi is a town in Bolivia known as a commercial and cultural center of the Aymara people near Lake Titicaca.
  • E. Guarequena
    Guarequena is an alternative name for the Warekena language, an indigenous Arawakan language spoken in parts of Brazil and Venezuela.
  • 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_69d6aac656d48190b275efaa7d6074ee completed April 8, 2026, 7:21 p.m.
NER Named-entity recognition batch_69d7e900fbcc8190a3177f8a73564433 completed April 9, 2026, 5:59 p.m.
NED1 Entity disambiguation (via context triple) batch_69e4cc4c630c8190a5e43c2108dfb50d completed April 19, 2026, 12:36 p.m.
Created at: April 8, 2026, 9:30 p.m.