Triple

T23061270
Position Surface form Disambiguated ID Type / Status
Subject Filipino alphabet E574307 entity
Predicate usedFor P98 FINISHED
Object Kapampangan 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: Kapampangan | Statement: [Filipino alphabet, usedFor, Kapampangan]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kapampangan
Context triple: [Filipino alphabet, usedFor, Kapampangan]
  • A. Kapampangan chosen
    Kapampangan is an Austronesian language spoken primarily in the Pampanga region of the Philippines by the Kapampangan ethnic group.
  • B. Ibanag
    Ibanag is an Austronesian language spoken primarily in the Cagayan Valley region of northern Luzon in the Philippines.
  • C. Sugbuanon
    Sugbuanon refers to the Cebuano people, a Visayan ethnolinguistic group from the central and southern Philippines known for speaking the Cebuano language.
  • D. 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.
  • E. Sugbu
    Sugbu is the pre-colonial name for the area that became Cebu City in the Philippines, a major coastal settlement and trading center in the Visayas.
  • 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_69e245ba7ae48190be606dbc54120e39 completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f1899ff96081908d89a07a3b1065c8 completed April 29, 2026, 4:31 a.m.
Created at: April 17, 2026, 3:55 p.m.