Triple

T8938917
Position Surface form Disambiguated ID Type / Status
Subject Makushi language E212846 entity
Predicate closelyRelatedTo P37 FINISHED
Object Pemon language E208122 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: Pemon language | Statement: [Makushi language, closelyRelatedTo, Pemon language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Pemon language
Context triple: [Makushi language, closelyRelatedTo, Pemon language]
  • A. Pemon language chosen
    Pemon language is an indigenous Cariban language spoken primarily by the Pemon people of southeastern Venezuela and neighboring regions of Brazil and Guyana.
  • B. 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.
  • C. Warao language
    The Warao language is an indigenous language isolate spoken by the Warao people of northeastern Venezuela and nearby regions, particularly in the Orinoco Delta.
  • D. Yucuna language
    The Yucuna language is an indigenous Arawakan language spoken by the Yucuna people of the Colombian Amazon.
  • E. Juruna language
    The Juruna language is an indigenous Tupian language spoken by the Juruna (Yudjá) people of the Xingu region in Brazil.
  • 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_69ca839694c88190b324ffeb43d23b08 completed March 30, 2026, 2:07 p.m.
NER Named-entity recognition batch_69cc66b7484481909e0d7610552f5386 completed April 1, 2026, 12:28 a.m.
NED1 Entity disambiguation (via context triple) batch_69cfc1eb308c81909f5be133c75ad568 completed April 3, 2026, 1:34 p.m.
Created at: March 30, 2026, 6:58 p.m.