Triple

T21605508
Position Surface form Disambiguated ID Type / Status
Subject Miyako language E533159 entity
Predicate hasDialect P4251 FINISHED
Object Ikema dialect 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: Ikema dialect | Statement: [Miyako language, hasDialect, Ikema dialect]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ikema dialect
Context triple: [Miyako language, hasDialect, Ikema dialect]
  • A. Ikema dialect chosen
    The Ikema dialect is a distinct variety of the Miyakoan (Ryukyuan) language spoken by the island community of Ikema-jima in Okinawa, Japan.
  • B. Kikai dialect
    The Kikai dialect is a regional variety of the Amami language spoken on Kikai Island in Japan’s Ryukyu archipelago.
  • C. Kamia dialect
    The Kamia dialect is a regional variety of the Ipai-Tipai language traditionally spoken by the Kamia (Kumeyaay) people of southern California and northern Baja California.
  • D. Raijua dialect
    The Raijua dialect is a regional variety of the Sawu language spoken on Raijua Island in eastern Indonesia, distinguished by its own phonological and lexical features.
  • E. Tomia dialect
    The Tomia dialect is a regional variety of the Tukang Besi language spoken on Tomia Island in Southeast Sulawesi, Indonesia.
  • 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_69e0c46364608190a337dc8720dc2a35 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69ef17e4a8088190bf51ab2af2369762 completed April 27, 2026, 8:01 a.m.
Created at: April 16, 2026, 6:33 p.m.