Triple

T11091315
Position Surface form Disambiguated ID Type / Status
Subject Davao Oriental E262260 entity
Predicate localLanguage P1252 FINISHED
Object Bisaya E45639 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: Bisaya | Statement: [Davao Oriental, localLanguage, Bisaya]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bisaya
Context triple: [Davao Oriental, localLanguage, Bisaya]
  • A. Binisaya chosen
    Binisaya is a major Austronesian language of the Philippines, widely spoken in the Central Visayas and parts of Mindanao.
  • B. Surigaonon Bisaya
    Surigaonon Bisaya is a Visayan language variety spoken primarily in Surigao and nearby areas in the northeastern part of Mindanao in the Philippines.
  • 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. 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. Waray language
    Waray is an Austronesian language spoken primarily in the Eastern Visayas region of the Philippines, particularly on Samar and nearby islands.
  • 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_69d6aa9a40d88190a373e2c7e48285db completed April 8, 2026, 7:20 p.m.
NER Named-entity recognition batch_69d799ebae8c8190987b474adb7ede47 completed April 9, 2026, 12:22 p.m.
NED1 Entity disambiguation (via context triple) batch_69e3e7c586808190a576803b7406a49e completed April 18, 2026, 8:21 p.m.
Created at: April 8, 2026, 9:27 p.m.