Triple
T18767362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ybanag |
E458925
|
entity |
| Predicate | ethnicGroup |
P194
|
FINISHED |
| Object | Ibanag |
—
|
NE NERFINISHED |
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: Ibanag | Statement: [Ybanag, ethnicGroup, Ibanag]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ibanag Context triple: [Ybanag, ethnicGroup, Ibanag]
-
A.
Ibanag
chosen
Ibanag is an Austronesian language spoken primarily in the Cagayan Valley region of northern Luzon in the Philippines.
-
B.
Malibcong
Malibcong is a remote, mountainous municipality in the Philippine province of Abra known for its indigenous communities and largely undeveloped natural landscapes.
-
C.
Kapampangan
Kapampangan is an Austronesian language spoken primarily in the Pampanga region of the Philippines by the Kapampangan ethnic group.
-
D.
Aguiguan
Aguiguan is a small, uninhabited island in the Northern Mariana Islands known for its rugged terrain and seabird colonies.
-
E.
Yakan
Yakan is an Austronesian language spoken primarily by the Yakan people of Basilan and nearby areas in the southern Philippines.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8d395dba0819087568404508590cb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e58d859c8081909cec3aa64d264885 |
completed | April 20, 2026, 2:20 a.m. |
Created at: April 10, 2026, 11:52 a.m.