Triple

T13453374
Position Surface form Disambiguated ID Type / Status
Subject Yucuna people E311167 entity
Predicate language P15 FINISHED
Object Yucuna language E168446 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: Yucuna language | Statement: [Yucuna people, language, Yucuna language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Yucuna language
Context triple: [Yucuna people, language, Yucuna language]
  • A. Yucuna language chosen
    The Yucuna language is an indigenous Arawakan language spoken by the Yucuna people of the Colombian Amazon.
  • B. Yukpa language
    The Yukpa language is an indigenous Cariban language spoken by the Yukpa people in the border regions of northeastern Colombia and western Venezuela.
  • C. Mayaimi language
    The Mayaimi language was the now-extinct indigenous language once spoken by the Mayaimi people around Lake Okeechobee in southern Florida.
  • D. Secoya language
    The Secoya language is a Western Tucanoan language spoken by the Secoya people of the Amazonian regions of Ecuador and Peru.
  • E. Wayana language
    The Wayana language is an indigenous Cariban language spoken by the Wayana people of the Guiana region in northeastern South America.
  • 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_69d806a938b8819097ec43a2229fc7f9 completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69dbaefae85481909e6a59797cbb25e7 completed April 12, 2026, 2:40 p.m.
NED1 Entity disambiguation (via context triple) batch_69f75d8892a88190b4a32865b32c8883 completed May 3, 2026, 2:36 p.m.
Created at: April 9, 2026, 9:41 p.m.