Triple
T6839687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Waray people |
E157539
|
entity |
| Predicate | nativeName |
P15
|
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: [Waray people, nativeName, Waray]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Waray Context triple: [Waray people, nativeName, 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.
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_69c6882c53608190b99aebef079b23bd |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d6b2ee248190991c3e827be75bb7 |
completed | March 27, 2026, 7:12 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c74271b9dc8190abbe3b1f9819c38f |
completed | March 28, 2026, 2:52 a.m. |
Created at: March 27, 2026, 2:19 p.m.