Triple

T15806054
Position Surface form Disambiguated ID Type / Status
Subject Bikol Central E383218 entity
Predicate closelyRelatedTo P37 FINISHED
Object Waray E335884 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: Waray | Statement: [Bikol Central, closelyRelatedTo, Waray]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Waray
Context triple: [Bikol Central, closelyRelatedTo, Waray]
  • A. Waray language
    Waray is an Austronesian language spoken primarily in the Eastern Visayas region of the Philippines, particularly on Samar and nearby islands.
  • B. Binisaya
    Binisaya is a major Austronesian language of the Philippines, widely spoken in the Central Visayas and parts of Mindanao.
  • C. Waray of Samar chosen
    Waray of Samar is a major regional language variety spoken on the island of Samar in the Eastern Visayas region of the Philippines.
  • D. Masbateño Bisaya
    Masbateño Bisaya is a Visayan language variety spoken primarily on Masbate Island in the Philippines, influenced by both Cebuano and Hiligaynon.
  • E. Ifugao languages
    The Ifugao languages are a group of closely related Austronesian languages spoken by the Ifugao people of the northern Philippines, particularly in the mountainous areas of Luzon.
  • 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_69d86da2858c819090cc8481e7207b6e completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e0b52682548190998d8b6a08982877 completed April 16, 2026, 10:08 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff998fa5588190b28efc2f342405aa completed May 9, 2026, 8:31 p.m.
Created at: April 10, 2026, 4:48 a.m.