Triple

T6777140
Position Surface form Disambiguated ID Type / Status
Subject Yine language E155585 entity
Predicate alternateName P39 FINISHED
Object Piro-Yine E619681 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: Piro-Yine | Statement: [Yine language, alternateName, Piro-Yine]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Piro-Yine
Context triple: [Yine language, alternateName, Piro-Yine]
  • A. Pira-Yine chosen
    Pira-Yine is an indigenous language of the Arawakan family spoken by the Yine people in the Amazonian region of Peru.
  • B. Yanaon
    Yanaon is the former name of Yanam, a small coastal town in India that was once part of French India and retains a distinct Franco-Indian cultural heritage.
  • C. Paquisha
    Paquisha is a locality in southeastern Ecuador known primarily for giving its name to the 1981 Paquisha War between Ecuador and Peru.
  • D. Yawal
    Yawal is a town in the Indian state of Maharashtra, situated in the Jalgaon district and known for its agricultural surroundings and local markets.
  • E. Puyuma
    Puyuma are an indigenous Austronesian ethnic group of southeastern Taiwan known for their distinct language, matrilineal social structure, and rich ceremonial traditions.
  • 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_69c688162bf8819088b664b5c3b5be7a completed March 27, 2026, 1:37 p.m.
NER Named-entity recognition batch_69c6d26725208190b64935cfd08b2aff completed March 27, 2026, 6:54 p.m.
NED1 Entity disambiguation (via context triple) batch_69c723c9b1cc81908f38f203acb86002 completed March 28, 2026, 12:41 a.m.
Created at: March 27, 2026, 2:13 p.m.