Triple

T517341
Position Surface form Disambiguated ID Type / Status
Subject Waray language E10736 entity
Predicate alternativeName P39 FINISHED
Object Waray-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-Waray | Statement: [Waray language, alternativeName, Waray-Waray]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Waray-Waray
Context triple: [Waray language, alternativeName, Waray-Waray]
  • A. Binisaya
    Binisaya is a major Austronesian language of the Philippines, widely spoken in the Central Visayas and parts of Mindanao.
  • B. Tagalog
    Tagalog is an Austronesian language primarily spoken in the Philippines and serves as the basis for the country’s national language, Filipino.
  • C. Bikol language
    The Bikol language is an Austronesian language spoken primarily in the Bicol Region of the Philippines, known for its several regional varieties and close relation to other Central Philippine languages.
  • D. Waray language chosen
    Waray is an Austronesian language spoken primarily in the Eastern Visayas region of the Philippines, particularly on Samar and nearby islands.
  • E. Kapampangan language
    Kapampangan is an Austronesian language of the Philippines primarily spoken in the Pampanga region of Central 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_69a2e84a0d08819087e01863fcd9abf1 completed Feb. 28, 2026, 1:06 p.m.
NER Named-entity recognition batch_69a2f19d81d48190bd65a02059fc8473 completed Feb. 28, 2026, 1:46 p.m.
NED1 Entity disambiguation (via context triple) batch_69a4a42b9a648190ab38c181da2ae0f6 completed March 1, 2026, 8:40 p.m.
Created at: Feb. 28, 2026, 1:12 p.m.