Triple

T8758119
Position Surface form Disambiguated ID Type / Status
Subject Pemon language E208122 entity
Predicate hasNeighboringLanguage P16383 FINISHED
Object Macushi language E212846 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: Macushi language | Statement: [Pemon language, hasNeighboringLanguage, Macushi language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Macushi language
Context triple: [Pemon language, hasNeighboringLanguage, Macushi language]
  • A. Makushi language chosen
    The Makushi language is an indigenous Cariban language spoken primarily by the Makushi people in northern Brazil and southern 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. Piapoco language
    The Piapoco language is an indigenous Arawakan language spoken by the Piapoco people of Colombia and Venezuela.
  • D. Awajún language
    Awajún language is an indigenous Jivaroan language spoken primarily by the Awajún (Aguaruna) people of northern Peru.
  • E. Yucuna language
    The Yucuna language is an indigenous Arawakan language spoken by the Yucuna people of the Colombian Amazon.
  • 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_69ca835cd6b08190bd7c63db92f53c86 completed March 30, 2026, 2:06 p.m.
NER Named-entity recognition batch_69cc5ddc2d9c81908948aee2b956cce4 completed March 31, 2026, 11:50 p.m.
NED1 Entity disambiguation (via context triple) batch_69cf434232d08190bfee6f5ec1c0b5a6 completed April 3, 2026, 4:34 a.m.
Created at: March 30, 2026, 6:40 p.m.