Triple

T16049479
Position Surface form Disambiguated ID Type / Status
Subject Hanunóo script E389314 entity
Predicate UnicodeBlock P1445 FINISHED
Object Hanunoo E174383 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: Hanunoo | Statement: [Hanunóo script, UnicodeBlock, Hanunoo]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hanunoo
Context triple: [Hanunóo script, UnicodeBlock, Hanunoo]
  • A. Hanunoo chosen
    Hanunoo is an indigenous Philippine script traditionally used by the Hanunó'o Mangyan people of Mindoro to write their Austronesian language.
  • B. Hinunangan
    Hinunangan is a coastal municipality in the province of Southern Leyte in the Philippines, known for its beaches and nearby island attractions.
  • C. Pangarang
    Pangarang is an alternative name for the Bangerang, an Aboriginal Australian people traditionally associated with regions of northern Victoria and southern New South Wales.
  • D. Guanito
    Guanito is a rural municipal district within the San Juan de la Maguana municipality in the San Juan Province of the Dominican Republic.
  • E. Guindulungan
    Guindulungan is a municipality in the province of Maguindanao in the Bangsamoro Autonomous Region in Muslim Mindanao 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_69d86dae698881908327ef2d67706cb9 completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e18361083c8190abc84534265dc992 completed April 17, 2026, 12:48 a.m.
NED1 Entity disambiguation (via context triple) batch_69ffdbe095908190ba10399ad6f3b5f8 completed May 10, 2026, 1:14 a.m.
Created at: April 10, 2026, 4:56 a.m.