Triple

T15654969
Position Surface form Disambiguated ID Type / Status
Subject Yanomami E376414 entity
Predicate speak P741 FINISHED
Object Yanomamö language E1169129 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: Yanomamö language | Statement: [Yanomami, speak, Yanomamö language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Yanomamö language
Context triple: [Yanomami, speak, Yanomamö language]
  • A. Yanomaman languages chosen
    The Yanomaman languages are a small family of indigenous languages spoken by the Yanomami peoples of the Amazon rainforest in southern Venezuela and northern Brazil.
  • 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. Yucuna language
    The Yucuna language is an indigenous Arawakan language spoken by the Yucuna people of the Colombian Amazon.
  • D. Pemon language
    Pemon language is an indigenous Cariban language spoken primarily by the Pemon people of southeastern Venezuela and neighboring regions of Brazil and Guyana.
  • E. Yawalapiti language
    The Yawalapiti language is an Arawakan language spoken by the Yawalapiti people of Brazil’s Upper Xingu region in the 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_69d85cd1564c8190991adda63bfab4b0 completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69e04ef1f83c8190bbf65eed162cbd55 completed April 16, 2026, 2:52 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff6ed4d9f88190b7e24bf84c5a916f completed May 9, 2026, 5:28 p.m.
Created at: April 10, 2026, 4:15 a.m.