Triple

T390199
Position Surface form Disambiguated ID Type / Status
Subject Latin America E8862 entity
Predicate hasIndigenousLanguage P4185 FINISHED
Object Quechua E3862 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: Quechua | Statement: [Latin America, hasIndigenousLanguage, Quechua]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Quechua
Context triple: [Latin America, hasIndigenousLanguage, Quechua]
  • A. Quechua chosen
    Quechua is an indigenous language family of the central Andes, historically associated with the Inca Empire and still widely spoken across several South American countries.
  • B. Aymara
    Aymara is an indigenous language spoken primarily by the Aymara people of the central Andes in countries such as Bolivia, Peru, and Chile.
  • C. Guaraní
    Guaraní is an indigenous South American language of the Tupi–Guaraní family, widely spoken in Paraguay and neighboring countries and notable for its strong cultural and national significance.
  • D. Aguaruna language
    The Aguaruna language is a Jivaroan language spoken by the Aguaruna (Awajún) people of northern Peru, closely related to the Shuar language of Ecuador.
  • E. Boliviano
    The Boliviano is the official monetary unit of Bolivia, used for everyday transactions and financial operations throughout the country.
  • 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_69a2e7f55c60819097aff65ea2ca2832 completed Feb. 28, 2026, 1:04 p.m.
NER Named-entity recognition batch_69a2ec5bdc848190826701590070497b completed Feb. 28, 2026, 1:23 p.m.
NED1 Entity disambiguation (via context triple) batch_69a4035310608190a1e0f807cb93e1e1 completed March 1, 2026, 9:13 a.m.
Created at: Feb. 28, 2026, 1:08 p.m.