Triple

T22851384
Position Surface form Disambiguated ID Type / Status
Subject Northern Ryukyuan language E566363 entity
Predicate hasVariety P455 FINISHED
Object Yoron language NE NERFINISHED

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: Yoron language | Statement: [Northern Ryukyuan language, hasVariety, Yoron language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Yoron language
Context triple: [Northern Ryukyuan language, hasVariety, Yoron language]
  • A. Yoron language chosen
    The Yoron language is a Ryukyuan language of the Japonic family spoken by the inhabitants of Yoron Island in Japan’s Kagoshima Prefecture.
  • B. Yoreme language
    The Yoreme language is an indigenous Uto-Aztecan language spoken by the Mayo (Yoreme) people of northern Mexico.
  • C. Oroch language
    The Oroch language is a critically endangered Tungusic language of the Russian Far East, traditionally spoken by the Oroch people along the lower Amur and nearby coastal areas.
  • D. Karkar-Yuri language
    Karkar-Yuri is a Papuan language of Papua New Guinea, spoken by the Karkar and Yuri peoples in the Sepik region.
  • E. Yugh language
    The Yugh language is an almost extinct Uralic (Samoyedic) language once spoken by the Yugh people along the Yenisei River in central Siberia.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e2458750b481908a8e4cf4609cc6cf completed April 17, 2026, 2:36 p.m.
NER Named-entity recognition batch_69f17eb8b3588190b2bc8e7021f9ef10 completed April 29, 2026, 3:44 a.m.
Created at: April 17, 2026, 3:36 p.m.