Triple

T13980473
Position Surface form Disambiguated ID Type / Status
Subject Itawit E336294 entity
Predicate hasNeighboringLanguage P16383 FINISHED
Object Ibanag E101548 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: Ibanag | Statement: [Itawit, hasNeighboringLanguage, Ibanag]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ibanag
Context triple: [Itawit, hasNeighboringLanguage, 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 (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_69d81c639e808190a0e4b4f3d31c6a59 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de2ea10dc88190b9720919a021e570 completed April 14, 2026, 12:10 p.m.
NED1 Entity disambiguation (via context triple) batch_69fbac9231888190ad8cb460db73bdb4 completed May 6, 2026, 9:03 p.m.
Created at: April 9, 2026, 10:18 p.m.