Triple

T7720646
Position Surface form Disambiguated ID Type / Status
Subject Amuesha language E174998 entity
Predicate hasAlternativeSpelling P457 FINISHED
Object Yaneša’ E628576 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: Yaneša’ | Statement: [Amuesha language, hasAlternativeSpelling, Yaneša’]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Yaneša’
Context triple: [Amuesha language, hasAlternativeSpelling, Yaneša’]
  • A. Yanešaʼ chosen
    Yanešaʼ is an Arawakan language spoken by the Yanesha people of the central Peruvian Amazon.
  • B. Nesuhi
    Nesuhi was a prominent Turkish-American record producer and music executive best known for his influential work in jazz, particularly at Atlantic Records.
  • C. Ypati
    Ypati is a historic town in central Greece, known for its mountainous setting near Mount Oeta and its role in various periods of Greek history.
  • D. Yasa'ur
    Yasa'ur was a Mongol prince and military leader who played a significant role in the politics and conflicts of the Chagatai Khanate during the early 14th century.
  • E. Yoreme
    Yoreme is the self-designation of the Mayo Indigenous people of northern Mexico, known for their rich cultural traditions, language, and ceremonial practices.
  • 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_69c6995d541c81909eaa646b1a8369a9 completed March 27, 2026, 2:51 p.m.
NER Named-entity recognition batch_69c702f0366c8190a78f0b03f090fc2c completed March 27, 2026, 10:21 p.m.
NED1 Entity disambiguation (via context triple) batch_69c8b517c64881908d24e8613dc33bf4 completed March 29, 2026, 5:13 a.m.
Created at: March 27, 2026, 4:05 p.m.