Triple

T3270917
Position Surface form Disambiguated ID Type / Status
Subject Biliran Island E68645 entity
Predicate localLanguage P1252 FINISHED
Object Waray E10736 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: [Biliran Island, localLanguage, Waray]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Waray
Context triple: [Biliran Island, localLanguage, Waray]
  • A. Waray language chosen
    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
    Waray of Samar is a major regional language variety spoken on the island of Samar in the Eastern Visayas region of the Philippines.
  • D. 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.
  • E. Butuanon language
    The Butuanon language is an Austronesian language spoken primarily in and around Butuan City in Mindanao, Philippines.
  • 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_69ad859b54f881909bf530d549caf2fd completed March 8, 2026, 2:20 p.m.
NER Named-entity recognition batch_69adaff4b9dc8190b7e3da0bbffccf99 completed March 8, 2026, 5:20 p.m.
NED1 Entity disambiguation (via context triple) batch_69b3341597448190805ff43effb9070c completed March 12, 2026, 9:45 p.m.
Created at: March 8, 2026, 3:09 p.m.